Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesService id from search results.
langNoLanguage of titles and booking pages: en, de, fr, es, it or pt. Default: the user's locale, else en.
currencyNoCurrency for prices: GBP (default), EUR, USD or AUD.

Output Schema

NameRequiredDescriptionDefault
as_ofYesWhen the free times were last refreshed.
noticeYes
serviceYes
medical_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / service / properties / stages / description
      Previous value: -"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."New value: +"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 = for people who know the practice well and make it their own, often sharing it (community, guiding others). Empty until Sissoo has sorted it."
  2. Changed1 schema field changed
    • removedOutput schema / properties / service / properties / levels
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  3. Changed1 schema field changed
    • 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"
      +}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description nonetheless adds real context the annotations don't: the response includes the next 6 free times, each carrying a deep link to the booking page with that date pre-selected. It stops short of saying what happens for an unknown id.

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?

A single front-loaded sentence with an enumerated payload list and zero filler. The identifying scope ('by its id') leads, and every clause contributes a concrete detail about what comes back.

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?

Given full schema coverage, an output schema, and annotations, this is close to complete: the agent knows the input, the safety profile, and the shape of the result including booking links. The only gap is failure behavior for a missing or invalid id.

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 100%, with defaults and the accepted language/currency values already documented in the schema, so a 3 is the baseline. The description adds only indirect meaning — that lang affects titles and booking pages and currency affects prices — without new syntax or constraint details.

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 names a specific verb-and-resource pair ('Details of one Sissoo session by its id') and enumerates the payload: description, practitioner, price, formats, languages, and the next 6 free times with booking links. That distinguishes it well from search_services or get_practitioner, though it never names those siblings explicitly.

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 parameter's schema note ('Service id from search results') suggests obtaining ids from search_services first, but the description itself says nothing about when to call this instead of next_free_times, which appears to cover overlapping availability data. No exclusions or prerequisites are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources