Conciergr Timetable

Book a trial child into a lesson

hold_trial_seat

Hold a trial seat for a child in one lesson of a class (class_id and date) or in a trial session (trial_session_id). First name and level only. Refused with the reason and the next dates that would work (no trials, not on that date, closed, notice, trial cap, full, level not taken).

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": {
      "child_first_name": "<child_first_name>",
      "level": "<level>"
    },
    "name": "hold_trial_seat"
  }
}

Input Schema

Name	Required	Description
`date`	No	The lesson's date (with class_id), YYYY-MM-DD, in the business's own time zone.
`level`	Yes	Level id or name.
`class_id`	No	The class.
`child_first_name`	Yes	Up to 40 characters.
`trial_session_id`	No	Or the trial session.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already state this is a non-read-only, non-destructive, closed-world operation. The description adds useful behavioral detail beyond annotations by listing refusal reasons and noting that a refusal returns the reason and next workable dates. It does not cover success return shape, duplicate-hold behavior, or expiry, so it is strong but not exhaustive.

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?

It is front-loaded with the action and then compactly states the two modes and refusal behavior. The parenthetical refusal list is dense but earns its place because it tells the agent exactly what failure conditions can occur.

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 non-destructive mutation with annotations and a fully described five-parameter schema, the description is almost complete: it explains modes and failure behavior. The main gap is that without an output schema, it does not describe the successful return value beyond the hold action itself.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameter descriptions already carry the baseline. The tool description adds meaningful conditional semantics by explaining that class_id and date form one mode while trial_session_id forms the other, and that only first name and level are accepted.

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?

The description uses a specific verb and resource: 'Hold a trial seat for a child.' It also clearly distinguishes the two supported booking modes, one lesson of a class vs. a trial session, so an agent can understand the action without reading sibling schemas.

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?

It gives clear context: use class_id and date for a lesson, or trial_session_id for a trial session, with first name and level only. It does not explicitly contrast this tool with siblings like release_trial_seat or add_trial_session, so it stops short of full when/when-not guidance.

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

All Conciergr Timetable 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?