Sissoo

Sissoo practitioner

get_practitioner

Read-onlyIdempotent

A Sissoo practitioner's public profile by practitioner id (from search results): name, place, session languages, service types and their bookable sessions, with a link to their Sissoo page. Practitioners' phone numbers, emails and addresses are private on Sissoo, so don't look them up elsewhere: people contact a practitioner through their Sissoo page.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Practitioner id from search results, e.g. "joyspace-therapy".
`lang`	No	Language of titles and booking pages: en, de, fr, es, it or pt. Default: the user's locale, else en.
`currency`	No	Currency for prices: GBP (default), EUR, USD or AUD.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	Yes	When the free times were last refreshed.
`notice`	Yes
`services`	Yes	Up to 10 sessions, soonest free first.
`medical_note`	No
`practitioner`	Yes
`more_sessions`	Yes	Further sessions on their Sissoo page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedOutput schema / properties / services / items / properties / stages

Added value: +{
+  "description": "Sissoo's 3 E's, where a client is with this kind of session: emerge alone = a first step for someone new to it; evolve alone = for going deeper (series, programmes, follow-ups); both = open to anyone; empower = community or guiding others. Empty until Sissoo has sorted it.",
+  "items": {
+    "enum": [
+      "emerge",
+      "evolve",
+      "empower"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: contact details are private and must not be sourced elsewhere. It doesn't state what happens with an unknown or malformed id, which would complete the picture.

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, front-loaded with the resource and its returned fields, followed by the privacy constraint that shapes agent behavior. No filler or redundancy.

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?

An output schema exists, so return-value documentation is not required, and the description covers the id's provenance and the privacy rule. What remains unstated is how the tool behaves on an invalid or missing practitioner id and how it relates to get_service.

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 all three parameters including lang and currency defaults are documented in the schema itself. The description only reinforces that id originates from search results and adds nothing about language or currency behavior, so the baseline 3 applies.

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?

States a specific verb and resource (retrieve a Sissoo practitioner's public profile by id) and enumerates what the profile contains: name, place, languages, service types with bookable sessions, and page link. It doesn't explicitly distinguish itself from the sibling get_service, but the practitioner-vs-service framing makes the resource boundary reasonably clear.

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?

Tells the agent where the id comes from ('from search results'), which establishes the intended lookup workflow, and adds a clear negative instruction: don't hunt for phone numbers, emails or addresses elsewhere because contact happens through the Sissoo page. It stops short of naming get_service as the alternative for service-level lookups.

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

All Sissoo 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?