Sissoo

Sissoo session details

get_service

Read-onlyIdempotent

Details of one Sissoo session by its id: description, practitioner, price, formats, session languages and the next 6 free times, each with a link to the booking page with that date picked.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Service id from search results.
`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
`service`	Yes
`medical_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedOutput schema / properties / service / 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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, non-destructive, so the safety profile is covered. The description adds genuine context beyond that — it discloses that the result includes the next 6 free times each with a pre-filtered booking link, which is a non-obvious behavioral trait. However, it says nothing about error behavior or what happens for a stale/invalid id.

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

Conciseness4/5

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

A single compact sentence, front-loaded with the core purpose before the field list. The field enumeration is slightly redundant with the output schema but stays within one sentence and earns most of its space.

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, annotations cover the safety profile, and the description still gives a useful preview of return content. For a simple 3-parameter read tool this is sufficient, with only usage routing to siblings left unaddressed.

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%, with each parameter (id, lang, currency) and its default/enum-ish values already documented in the schema. The description adds no meaning beyond that, so baseline 3 applies; 'session languages' refers to session data, not the lang parameter, and could even confuse slightly.

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 ('Details of one Sissoo session by its id') and enumerates the fields returned, so the agent knows exactly what it gets. It does not explicitly differentiate itself from siblings like search_services or get_practitioner, but the 'one session by id' scoping is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the id must come from search results, and the description never says when to call this versus get_practitioner or next_free_times. There are no exclusions or prerequisites stated in the description itself.

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?