Skip to main content
Glama

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, addresses, personal websites and social media profiles are private on Sissoo, so don't look them up elsewhere: people contact a practitioner through their Sissoo page.

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_practitioner"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPractitioner id from search results, e.g. "joyspace-therapy".
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
servicesYesUp to 10 sessions, soonest free first.
medical_noteNo
practitionerYes
more_sessionsYesFurther sessions on their Sissoo page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / services / items / 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
    • 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"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing a data boundary: phone numbers, emails, addresses, personal sites and social profiles are deliberately absent, and the agent should not attempt to source them elsewhere. It does not discuss lookup failure modes or limitations on session data.

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?

Two sentences, front-loaded with the purpose and followed by a single actionable constraint; nothing is redundant. The first sentence is long due to the field enumeration, but each element reflects actual returned content rather than filler.

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?

An output schema exists, so return values need not be explained, yet the description still summarizes them usefully; parameters and defaults are covered by the schema. For a three-parameter read-only lookup, the addition of the privacy/contact boundary closes the only real ambiguity an agent would face.

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%, so each parameter is already documented in the schema, including the id's origin example and the lang/currency options. The description reinforces only the id's provenance ('from search results') and says nothing about how lang or currency affect returned titles and prices beyond what the schema states. Baseline 3 applies.

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?

Uses a specific verb and resource ('a Sissoo practitioner's public profile by practitioner id') and enumerates the returned content (name, place, session languages, service types, bookable sessions, link). It is clearly distinguishable from siblings such as get_service and search_services, which deal with services rather than practitioners.

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?

States the input's origin ('from search results'), which tells the agent this is a detail-follow-up call after a search rather than an entry point. It also sets a boundary on what to do when contact data is missing, but names no explicit alternative tool or exclusion condition.

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