Conciergr Timetable

Move a class to a new day or time from a date

change_class_time

From from_date on, the class runs on a new weekday or at new times: the old class ends the day before and a new one starts, seats carried across, so past dates stay as they were.

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>",
      "from_date": "<from_date>",
      "weekday": "<weekday>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "change_class_time"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The class's id.
`end`	Yes	New end, 24-hour HH:MM, e.g. 16:30.
`start`	Yes	New start, 24-hour HH:MM, e.g. 16:30.
`weekday`	Yes	1 = Monday ... 7 = Sunday.
`from_date`	Yes	The first date at the new time, YYYY-MM-DD, in the business's own time zone.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: the old class ends the day before, a new one starts, seats are carried across, and past dates remain unchanged. This discloses the temporal splitting and data-preservation behavior clearly, which is valuable for a mutation tool whose annotations only state it is not read-only and not destructive.

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?

The description is a single dense sentence that front-loads the from_date scoping and then explains the consequence. It is efficient, though the opening 'From from_date on' is slightly awkward.

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 mutation tool with annotations covering safety and a fully documented schema, the description provides enough behavioral context: what the operation does to the existing class and how seats and past dates are handled. It does not mention permissions or error cases, but those gaps are minor given the structured fields.

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 description coverage is 100%, so the schema already documents every parameter in detail. The description reinforces the meaning of from_date ('from from_date on') and implies weekday/time changes, but it does not add syntax or format details beyond what the schema provides.

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 states a specific schedule change operation: the class moves to a new weekday or new times from a given date. It is clear what the tool does, though it does not explicitly distinguish itself from sibling edit_classes or save_class.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as edit_classes, nor any prerequisites or exclusions. The description implies a scheduling-change context but leaves the agent to infer when this is the correct choice.

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?