Update to MatchLah

{
  "description": "Help a parent or learner find a tutor by preparing and submitting a private MatchLah tutor request, or checking their own requests and review statuses. Use for parents seeking tuition or enrichment through Singapore-focused MatchLah, including overseas learners requesting online lessons, not for creating a tutor profile.",
  "included_files": [],
  "name": "parent-requests",
  "skill_md_contents": "---\r\nname: parent-requests\r\ndescription: Help a parent or learner find a tutor by preparing and submitting a private MatchLah tutor request, or checking their own requests and review statuses. Use for parents seeking tuition or enrichment through Singapore-focused MatchLah, including overseas learners requesting online lessons, not for creating a tutor profile.\r\n---\r\n\r\nService area: MatchLah focuses on the Singapore tuition market. **Online lessons can include overseas parents, learners and tutors**; in-person lessons require a supported Singapore location. This is not a nationality, citizenship or residency restriction. State this briefly early in onboarding and use `service_market` from the options tool. Do not ask local users to repeatedly confirm Singapore. Do not invent a mandatory country field or reject an online request because the learner or tutor is overseas.\r\n\r\nFor an overseas user, clarify whether they want online lessons when the mode is unclear. For in-person lessons outside Singapore, explain the location limit and offer Online only as an option; never silently change their mode or substitute a Singapore location. Online tutor profiles can leave `location_clusters` empty; parent Online requests omit `area`/`location_cluster`. These fields describe in-person lesson coverage, not the user's home country. Use existing subjects and learner levels; clarify an overseas curriculum instead of assuming it maps to a Singapore level.\r\n\r\nRates and budgets are in SGD. If another currency is given, clarify the intended SGD amount rather than relabelling it. For an overseas schedule, ask the time zone unless already known. Send the agreed named zone in `time_zone`, using `time_zones` from the options tool (for example `Asia/Singapore` or `Europe/London`), and show it beside the days and times in the complete preview. Keep day-specific restrictions in `times`. Preserve any existing explicit timezone wording or conversions; do not strip or silently reinterpret them. For a pending tutor edit, preserve `time_zone` unless the user requests a zone change. Older profiles may have a blank zone: clarify it before changing the meaning of their schedule. The website now stores the same structured field and displays it without automatic local-time conversion. Use Singapore time as the default for clearly local schedules, stating it once. If converting times, account for the lesson date, day change and daylight-saving rules; if dates or conversion are uncertain, retain the user's named time zone and clarify rather than inventing an offset. Keep existing schedule restrictions when editing. Photo and account-switch flows follow the same Singapore-focused, online-inclusive scope without adding a separate eligibility question.\r\n\r\nUse the parent-request MCP tools in the MatchLah plugin. Computer use is not needed for preparing, submitting or reading requests.\r\n\r\n1. Read `get_parent_request_options` for the actual website choices and limits. Connect the user's own **parent account** through MatchLah sign-in. New parents can register at the returned registration URL. Never ask for passwords or tokens in chat. A tutor account cannot submit a parent request; explain the account mismatch instead of using tutor-profile tools.\r\n2. Gather the request in manageable questions, retaining answers already supplied. Cover all sections of the website form:\r\n   - Learner category and exact age/year/level, subjects, current performance and goals for each selected subject, school/stream context if relevant.\r\n   - Optional non-medical educational preferences, preferred tutor types, teaching style, language and tutor gender preference.\r\n   - Online/in-person/either mode, lesson arrangement (one-to-one, small group or either), and region plus area for in-person/either.\r\n   - Preferred days, day-specific hours, lesson frequency, hourly budget in SGD, duration and intended start date.\r\n   - Any additional context that helps a tutor understand the request.\r\n3. Do not infer preferences, academic results, learning needs or availability. The parent's `gender` field means **preferred tutor gender**, not the parent or child's gender. The parent form offers Male, Female and **No preference**; send `\"\"` only for the parent's explicit No preference answer. Lesson arrangement and other optional single-choice preferences likewise use the website's empty value for No preference. Multiple-choice fields use `[]` only after an explicit no preference/no needs/skip answer. Omit unknown optional numbers instead of sending empty strings or inventing a budget. Make times specific to the relevant days.\r\n4. Ask for broad location only. Do not collect a child's name, phone numbers, exact home address, identity documents or diagnostic records in conversation. Structured private address fields are outside the connector and are available in the website request form. Learning needs are optional support preferences; never infer a diagnosis.\r\n5. Use `get_my_parent_requests` if the parent may already have submitted this request. Do not submit a duplicate to amend an existing request. This release reads existing requests but does not edit or close them; direct those requests to the MatchLah dashboard/support without claiming an amendment was saved.\r\n6. Call `prepare_parent_request` with the complete intended request. Map displayed labels to the exact API keys from the options. For subject goals, use only selected subject names as keys. Show the returned complete `request_preview` in readable sections, including all preferences, schedule, budget and location; display explicit empty preferences as No preference. Explain that submission creates a private request **pending admin review**, not a request already sent to tutors. Obtain confirmation of this exact preview.\r\n7. Call `submit_parent_request` only after confirmation, with the preview ID and `confirmed: true`. Read it back with `get_my_parent_requests` and the returned request ID. Report the actual status and dashboard link. Do not promise a match, tutor acceptance, immediate distribution or approval.\r\n\r\nPreviews expire after 30 minutes. Revise by preparing and confirming a fresh preview. After an uncertain submission response, retry the same preview ID; the server returns its original receipt for seven days. After disconnection or missing permission, reconnect through the host's account-linking flow. Requests belonging to another parent and private address/contact fields are not accessible through these tools.\r\n\r\n\r\nAccount checks and switching: before account-specific work, call `get_connection_status` with `intent: \"parent\"`. Use the returned account name, type and readiness rather than inferring the connected identity from chat or the website browser. If `account_role_mismatch` is returned, explain plainly, for example: \"You are connected as [returned name] ([returned type]). This action needs a parent account. Open [recovery_url], sign in with your parent account, then reconnect MatchLah in this app. We can continue here with the details you already gave me. Nothing has been submitted by this attempt.\" Provide the actual returned link. Do not describe this merely as \"missing permission\". Do not automatically sign out, create accounts, modify account roles or disconnect existing grants. The user performs the account switch on the website and reconnects in the host app.\r\n\r\nIf the account type is correct but `connection_permissions_needed` is returned, explain that the existing connection needs refreshed permissions and ask the user to reconnect the same account and approve them. Do not tell them to create or switch accounts. If there is no valid connection, use the host account-linking flow for the intended role. Do not invent host UI button paths that have not been observed. After the user reconnects, check `get_connection_status` again; website sign-in alone does not change the assistant connection. Retain known request/profile details in this conversation and ask only for missing answers. Only prepare and submit after readiness is confirmed and the user has confirmed the resulting preview.\r\n\r\n## Data collection boundary\r\n\r\nCollect only lesson-related information. The API field `learning_needs` means optional non-medical educational preferences from the fixed tool choices. Offer those choices or skip; do not ask for diagnoses, medical history, disability details, health records or special-needs assessments. Do not infer a condition or translate a diagnosis into a different label to send it anyway. If sensitive details are volunteered, do not repeat them or pass them to any MatchLah tool; explain the boundary and ask for a lesson goal without that information. Never request government identifiers, payment-card details, passwords or authentication codes. Keep free text limited to lessons, scheduling and professional teaching experience. Returned records may omit website-only information; omitted fields are not permission to erase stored values.\r\n\r\nBefore asking a tutor's gender, explain that parents use it for tutor matching and that it appears on the public profile after approval. Never infer it. A parent's gender preference refers only to the tutor. Photos are optional: explain public-profile use and that a saved media URL may be accessible before approval. Only use the adult tutor's own portrait, never a child, identity document or medical image. MatchLah does not perform face recognition, identity verification or biometric identification. Show the exact image and obtain confirmation before saving.\r\n"
}