mental-health-care

Book an Appointment

book_appointment

Read-only

CRITICAL: Returns a booking URL — DO NOT navigate the user programmatically. Hand the URL to the user and let them click through. Pre-fills provider, time slot, state, and insurance for ~2-minute checkout.

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
`date_time`	Yes	Time slot string from check_availability (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
`provider_id`	Yes
`appointment_type`	Yes

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 (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 (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"
+]

Changed2 schema fields changedMay 9, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / appointment_type / enum

Previous value: -[
-  "354092",
-  "446840",
-  "465593",
-  "446841",
-  "449671"
-]New value: +[
+  "354092",
+  "446840",
+  "446841",
+  "449671",
+  "465593"
+]

Changed2 schema fields changedApr 27, 2026

changedInput schema / properties / date_time / description

Previous value: -"Time slot string from check_availability (e.g. \"2026-04-27 13:00:00 -0400\"). Pass exactly as received."New value: +"Time slot string from check_availability (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."

changedInput schema / required

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

First observedApr 26, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description goes beyond the readOnlyHint annotation by explaining exactly what the tool returns and how it behaves: it returns a URL rather than completing the booking, and it avoids programmatic navigation. This is critical, non-obvious behavioral context.

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?

Two sentences with no filler. The critical behavior and user-handling instruction are front-loaded, and every sentence adds value.

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?

With no output schema, the description correctly discloses the return value (a booking URL) and the required user flow. It is missing a bit of context around appointment_type and how this tool relates to check_availability, but the schema covers some of those details.

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 coverage is only 33%, so the description should compensate. It clarifies that provider, time slot, state, and insurance are pre-filled in the URL, but it does not explain the required appointment_type parameter or the meaning of its enum values.

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 core action: returns a booking URL and pre-fills checkout fields. It is specific about the resource (appointment booking) but does not explicitly differentiate itself from sibling tools like book_matching_session.

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?

The description gives strong operational guidance: do not navigate the user programmatically, hand the URL to the user, and let them click through. However, it does not state when to prefer this tool over book_matching_session or other alternatives.

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?