mental-health-care

Book a Clinical Matching Session

book_matching_session

Read-only

CRITICAL: provider_id is REQUIRED. Always call find_provider first (with appointment_type='446840' for the Clinical Matching Session) to get a specific intake specialist, then pass that provider_id here. Returns a pre-filled booking URL — do NOT navigate the user programmatically.

Input Schema

TableJSON Schema

Name	Required	Description
`agent`	No	Optional. Your agent or product name, e.g. "chatgpt", "claude-desktop", "acme-scheduler". It is written into the returned booking URL as utm_source so we can tell agent-referred families from direct traffic. MCP clients that send clientInfo on initialize are already identified and can omit this.
`state`	Yes	U.S. state where the client resides.
`date_time`	Yes	Time slot string from check_availability for the chosen intake specialist (e.g. "2026-04-27T13:00:00-04:00"). REQUIRED — the booking form is stuck on step 1 without it. Pass exactly as received from check_availability.
`insurance`	No	Insurance plan name. Pre-fills the form so verification runs faster at checkout.
`client_age`	No	Client age in years (0–25+).
`provider_id`	Yes	Healthie ID of the intake specialist. Get this from find_provider with appointment_type='446840'. REQUIRED — never construct the URL without it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / agent

Added value: +{
+  "description": "Optional. Your agent or product name, e.g. \"chatgpt\", \"claude-desktop\", \"acme-scheduler\". It is written into the returned booking URL as utm_source so we can tell agent-referred families from direct traffic. MCP clients that send clientInfo on initialize are already identified and can omit this.",
+  "type": "string"
+}

Changed1 schema field changedAug 29, 2026

changedInput schema / properties / insurance / enum

Previous value: -[
-  "Cash Pay",
-  "Aetna",
-  "Anthem Blue Cross",
-  "Baylor Scott & White",
-  "Blue Cross Blue Shield",
-  "ChampVA",
-  "Cigna",
-  "Florida Blue",
-  "Magellan",
-  "Medical Mutual",
-  "United Healthcare",
-  "Optum",
-  "Oscar",
-  "Tricare",
-  "Tricare West",
-  "UMR"
-]New value: +[
+  "Cash Pay",
+  "Aetna",
+  "Anthem Blue Cross",
+  "Blue Cross Blue Shield",
+  "ChampVA",
+  "Cigna",
+  "Florida Blue",
+  "Magellan",
+  "Medical Mutual",
+  "United Healthcare",
+  "Optum",
+  "Oscar",
+  "Tricare",
+  "Tricare West",
+  "UMR"
+]

Changed1 schema field changedAug 26, 2026

changedInput schema / properties / state / enum

Previous value: -[
-  "Florida",
-  "Texas",
-  "Illinois",
-  "North Carolina",
-  "Ohio",
-  "Missouri",
-  "Arizona",
-  "Georgia",
-  "Wisconsin",
-  "South Carolina",
-  "Indiana"
-]New value: +[
+  "Florida",
+  "Texas",
+  "Illinois",
+  "North Carolina",
+  "Georgia",
+  "Ohio",
+  "Missouri",
+  "Arizona",
+  "Wisconsin",
+  "South Carolina",
+  "Indiana"
+]

Changed1 schema field changedAug 13, 2026

changedInput schema / properties / insurance / enum

Previous value: -[
-  "Cash Pay",
-  "Aetna",
-  "Anthem Blue Cross",
-  "Baylor Scott & White",
-  "Blue Cross Blue Shield",
-  "ChampVA",
-  "Cigna",
-  "Florida Blue",
-  "Magellan",
-  "United Healthcare",
-  "Optum",
-  "Oscar",
-  "Tricare",
-  "Tricare West",
-  "UMR"
-]New value: +[
+  "Cash Pay",
+  "Aetna",
+  "Anthem Blue Cross",
+  "Baylor Scott & White",
+  "Blue Cross Blue Shield",
+  "ChampVA",
+  "Cigna",
+  "Florida Blue",
+  "Magellan",
+  "Medical Mutual",
+  "United Healthcare",
+  "Optum",
+  "Oscar",
+  "Tricare",
+  "Tricare West",
+  "UMR"
+]

Changed1 schema field changedJul 31, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedJun 29, 2026

changedInput schema / properties / date_time / description

Previous value: -"Time slot string from check_availability for the chosen intake specialist (e.g. \"2026-04-27 13:00:00 -0400\"). REQUIRED — the booking form is stuck on step 1 without it. Pass exactly as received from check_availability."New value: +"Time slot string from check_availability for the chosen intake specialist (e.g. \"2026-04-27T13:00:00-04:00\"). REQUIRED — the booking form is stuck on step 1 without it. Pass exactly as received from check_availability."

Changed1 schema field changedJun 3, 2026

changedInput schema / properties / state / enum

Previous value: -[
-  "Florida",
-  "Texas",
-  "Illinois",
-  "North Carolina",
-  "Ohio",
-  "Missouri",
-  "Arizona",
-  "Georgia",
-  "Wisconsin",
-  "South Carolina"
-]New value: +[
+  "Florida",
+  "Texas",
+  "Illinois",
+  "North Carolina",
+  "Ohio",
+  "Missouri",
+  "Arizona",
+  "Georgia",
+  "Wisconsin",
+  "South Carolina",
+  "Indiana"
+]

Changed1 schema field changedMay 9, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```

Changed3 schema fields changedApr 27, 2026

changedInput schema / properties / date_time / description

Previous value: -"Optional. If the user has already chosen a slot from check_availability for the matching-session intake type, pass it here. Otherwise the booking page lets the user pick."New value: +"Time slot string from check_availability for the chosen intake specialist (e.g. \"2026-04-27 13:00:00 -0400\"). REQUIRED — the booking form is stuck on step 1 without it. Pass exactly as received from check_availability."

addedInput schema / properties / provider_id

Added value: +{
+  "description": "Healthie ID of the intake specialist. Get this from find_provider with appointment_type='446840'. REQUIRED — never construct the URL without it.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "state"
-]New value: +[
+  "provider_id",
+  "state",
+  "date_time"
+]

First observedApr 26, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the tool is read-only in effect: it returns a pre-filled booking URL and instructs the agent not to navigate the user programmatically. This complements the readOnlyHint annotation with concrete output and action constraints, though it does not explicitly state that no appointment is reserved until the user completes the form.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a compact paragraph that front-loads the most critical constraint (provider_id required) and the ordering before explaining the output and navigation caution. Every sentence carries operational value with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with a full schema, the description captures the main invocation sequence, the output, and a key safety constraint. It does not mention the required state/date_time fields or how to present the returned URL, but the schema and annotations cover those gaps acceptably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is a 3. The description reinforces provider_id's source and the required sequence, but those details also appear in the schema's provider_id description; it adds little new parameter-level meaning beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the output (pre-filled booking URL) and the target resource (Clinical Matching Session via provider from find_provider), going beyond the generic title. It does not explicitly contrast with the sibling book_appointment, but the 'do NOT navigate' and 'returns URL' wording mark the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit use-before flow: call find_provider with appointment_type='446840' first, then pass the returned provider_id. It does not provide when-not-to-use guidance or mention alternative tools, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mental-health-care tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?