Skip to main content
Glama

Search Sissoo sessions

search_services
Read-onlyIdempotent

Finds bookable holistic and wellbeing sessions on Sissoo (sissoo.com), from reiki, massage and yoga to coaching, counselling and psychotherapy, online or in person, in several languages. Matches a short description of what the person is looking for, with optional place, format, session language, timing, budget and stage (new to it, or going deeper). Returns up to 8 sessions with price (booking fee included), next free time and a link to the service page with that date picked. Read-only: booking and payment happen on sissoo.com. Not for emergencies or crisis support: crisis wording returns helplines instead of sessions.

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": {
      "need": "<need>"
    },
    "name": "search_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of titles and booking pages: en, de, fr, es, it or pt. Default: the user's locale, else en.
needYesWhat the person is looking for, in a few of their own words: a type of session ("reiki", "life coaching") or what they hope for ("sleep better", "less stress"). No names or health records.
placeNoCity or country, for in-person sessions.
stageNoWhere the person is with this kind of session (Sissoo's 3 E's). emerge: new to it or trying it for the first time; first steps (free intro calls, first sessions) come first and repeats, follow-ups and programmes are left out. evolve: has tried it and wants to go deeper; programmes, series and follow-ups come first. Leave it out when they haven't said.
formatNoOnline, in person or either (default).
currencyNoCurrency for prices: GBP (default), EUR, USD or AUD.
max_priceNoHighest price per session in the chosen currency, booking fee included.
within_daysNoOnly sessions with a free time within this many days.
session_languageNoLanguage the session is held in, as a two-letter code, e.g. "de".

Output Schema

NameRequiredDescriptionDefault
as_ofYesWhen the free times were last refreshed.
countYes
crisisYesSet when the words suggest self-harm or an emergency: helplines instead of sessions.
noticeYes
resultsYes
crisis_noteNoHelplines, set whenever talking therapies are listed.
medical_noteNo
suggested_typesNoService types on Sissoo, when nothing matched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / results / 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. Changed2 schema fields changed
    • addedInput schema / properties / stage
      Added value: +{
      +  "description": "Where the person is with this kind of session (Sissoo's 3 E's). emerge: new to it or trying it for the first time; first steps (free intro calls, first sessions) come first and repeats, follow-ups and programmes are left out. evolve: has tried it and wants to go deeper; programmes, series and follow-ups come first. Leave it out when they haven't said.",
      +  "enum": [
      +    "emerge",
      +    "evolve"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / 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.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's extra context is genuine value: it caps results at 8, says prices include the booking fee, gives the next free time and a date-picked deep link, and discloses the non-obvious crisis-wording fallback to helplines. It does not describe no-match or partial-match behavior, so not a 5.

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?

Three front-loaded sentences with no filler; the purpose, optional facets, return shape, and the safety caveat each earn their place. The session-type enumeration (reiki, massage, yoga, coaching, counselling, psychotherapy) is slightly long but communicates catalog breadth.

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 an output schema and full annotation coverage, the description only needs to supply intent, scope, and quirks, and it does. Minor gaps remain around what happens when nothing matches and whether results are strictly ranked, but an agent has everything needed to call it correctly.

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% and the per-field descriptions (notably stage's emerge/evolve semantics) are richer than the prose. The description adds a useful conceptual summary of the optional facets and the 'new to it, or going deeper' gloss on stage, but no syntax or defaults beyond the schema, so the 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?

States a specific verb (Finds) and resource (bookable holistic and wellbeing sessions on Sissoo), enumerates the domain scope, and makes clear this is a discovery/search tool rather than a lookup of one service or practitioner, which is what get_service and get_practitioner imply.

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?

Explains the input shape ('a short description of what the person is looking for') and the optional narrowing facets, and gives an explicit when-not: emergencies or crisis support, where crisis wording returns helplines instead. It does not name sibling tools to route to for follow-up detail, so it falls just short of a 5.

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