Skip to main content
Glama

Occasions and storylines

list_occasions
Read-onlyIdempotent

Occasions (birthday, Christmas, Sinterklaas, new sibling, bedtime story...) with ready-made storylines for a personalised children's book, in the user's language. The stories suit children of about 2 to 8. Do not ask for the child's age, name or photo: just ask which story they like.

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": {
      "language": "<language>"
    },
    "name": "list_occasions"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesTwo-letter code of the language the user writes in, e.g. 'en', 'nl', 'de'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world call, so the description is not needed for the safety profile. It still adds real behavioral information beyond them: the results are localized to the user's language, the content targets children roughly 2 to 8, and it explicitly forbids interrogating the user for age, name, or photo. That last constraint is the kind of interaction rule annotations cannot express.

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 short sentences with no filler: the resource and its scope come first, followed by the interaction constraint. Every clause carries information an agent can act on.

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?

For a single-parameter read-only listing with no output schema, the description covers what the content is, who it is for, and how to handle the user interaction. The only gap is any hint about the shape of the returned items (e.g. how storylines are labelled), which is minor for a simple listing tool.

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?

There is one parameter at 100% schema coverage, and the schema already explains that 'language' is the two-letter code the user writes in. The description's phrase 'in the user's language' reinforces that this is the user's language rather than the book's target language, but adds little beyond the schema text, 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?

The description names the resource concretely and illustrates it with examples (birthday, Christmas, Sinterklaas, new sibling, bedtime story), so an agent knows it returns occasions paired with ready-made storylines. It never states the verb explicitly ('list') and does not contrast itself with the siblings create_book_plan or show_styles, so it falls short of a 5.

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?

The sentence 'just ask which story they like' implies the intended flow: show the options and let the user choose. There is no explicit when-to-use rule, no mention of what to do after selection (e.g. create_book_plan), and no exclusion of the sibling tools, so the guidance is implied rather than 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