therapy-booking

Check availability

check_availability

Read-onlyIdempotent

Real open start times (IST) for a session type over a date range (YYYY-MM-DD, at most 14 days): days (all times) and by_psychologist (each psychologist's own times, with slug, name and role). Past times and times starting within 10 minutes are never listed. Times are not held until create_booking_draft. Use mode 'in_person' for the Kakkanad clinic (individual sessions, Teresa James). ElloMind matches clients to a psychologist: offer a specific person only when the customer asks for one (by name, or the same psychologist as before); pass psychologist to see only theirs. If this tool returns an error, never tell the customer they are fully booked.

Input Schema

Name	Required	Description
`to`	Yes	end date YYYY-MM-DD
`from`	Yes	start date YYYY-MM-DD
`mode`	No	default online
`psychologist`	No	slug from by_psychologist (e.g. 'nithya-s'), only if the customer asked for that person
`session_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026
- addedInput schema / properties / from / maxLength
```
Added value: +10
```
- addedInput schema / properties / psychologist / maxLength
```
Added value: +64
```
- addedInput schema / properties / to / maxLength
```
Added value: +10
```

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / mode

Added value: +{
+  "description": "default online",
+  "enum": [
+    "online",
+    "in_person"
+  ],
+  "type": "string"
+}

addedInput schema / properties / psychologist

Added value: +{
+  "description": "slug from by_psychologist (e.g. 'nithya-s'), only if the customer asked for that person",
+  "type": "string"
+}

First observedSep 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial traits beyond annotations: IST timezone, 14-day max range, 10-minute buffer for start times, no reservation behavior, clinic-specific mode semantics, and error-handling guidance. These enrich the agent's understanding without contradicting the read-only, idempotent annotations.

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?

Information-dense and front-loaded with purpose; each sentence adds necessary detail (output structure, constraints, mode, psychologist, error handling). No wasted language; appropriate for a tool with no output schema.

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

Completeness5/5

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

Given no output schema, the description explains return structure (`days` and `by_psychologist` with slug, name, role), covers constraints, timezone, error handling, and domain logic. Complete for an agent to call it correctly.

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

Parameters4/5

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

Schema coverage is 80% (baseline 3), and the description adds meaningful constraint (14-day range) and clarifies mode and psychologist behavior beyond schema descriptions. It does not enumerate session_type values, but the schema enum covers that.

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

Purpose5/5

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

The description states a specific verb+resource: 'Real open start times (IST) for a session type over a date range', and distinguishes from create_booking_draft by noting times aren't held until then. An agent can identify the tool's function from the first sentence.

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?

Provides clear when-to-use context for mode (in_person for Kakkanad clinic) and psychologist (only when the customer asks for one), plus an alternative (create_booking_draft for holding times). Lacks explicit routing against other siblings like get_booking_status, but the context is strong and actionable.

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

All therapy-booking 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?