Conciergr Timetable

Add or change one class

save_class

Destructive

Add one class, or change one (give its id; send only the fields to change). Changing a class rewrites it for every date, past ones included: to move a class to another day or time from a date, use change_class_time. Seats are changed with set_seats. Needs the classes tick at the branch (both branches when moving it).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`id`	No	The class to change; leave out to add one.
`end`	No	End, 24-hour HH:MM, e.g. 16:30.
`mode`	No	in_person (the default), online or hybrid.
`room`	No	Room, up to 60 characters.
`start`	No	Start, 24-hour HH:MM, e.g. 16:30.
`weekday`	No	1 = Monday ... 7 = Sunday.
`capacity`	No	Class size (0 to 500); null for not set. Places left = capacity - seats taken - trial children that day.
`branch_id`	No	The branch it runs at (an id from list_branches).
`level_ids`	No	The levels it takes (ids from list_levels); at least one.
`last_month`	No	The last month it runs (always set; carry it forward when the run ends), YYYY-MM.
`first_month`	No	The first month it runs, YYYY-MM.
`seats_taken`	No	Seats taken, only when adding a class (0 to 500).
`subject_ids`	No	The subjects it teaches (ids from list_subjects); at least one.
`teacher_ids`	No	Its teachers (ids from list_teachers).
`takes_trials`	No	Whether families can ask about a trial in this class (default true).
`last_lesson_date`	No	Optional exact last lesson (in last_month, on its weekday), YYYY-MM-DD, in the business's own time zone.
`first_lesson_date`	No	Optional exact first lesson (in first_month, on its weekday), YYYY-MM-DD, in the business's own time zone.
`trial_notice_days`	No	Days of notice a trial needs (0 to 90).
`trial_cap_per_lesson`	No	Most trial children in one lesson; null for no cap.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, it discloses the critical mutation behavior that a change rewrites the class for every date, past ones included. It also exposes prerequisites and the branch-move permission condition, which are essential for safe invocation.

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 four dense sentences with no filler, front-loading the core add/change behavior and then immediately stating the destructive scope and alternatives. Every sentence carries actionable information.

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?

For a 19-parameter mutation tool with full schema descriptions and destructive annotations, the description covers the important behavioral context: scope of rewrite, partial-update semantics, alternatives, and branch prerequisites. Return values are not described, but no output schema exists and the tool is callable correctly without that detail.

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 schema already documents all 19 parameters thoroughly. The description adds useful conditional semantics not fully captured by the schema, especially that only fields being changed should be sent, and it clarifies the id/no-id add-vs-change behavior.

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 states a specific verb and resource: add one class or change one class. It distinguishes the single-class scope from bulk siblings like add_classes and names the specialized siblings change_class_time and set_seats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says how to use the tool for changes (provide id and send only changed fields) and routes the agent to alternatives for moving a class's day/time and for seats. It also names a concrete prerequisite: the classes tick at the branch, including both branches when moving.

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?