Conciergr Timetable

Every lesson at a branch

list_branch_lessons

Read-only

Every lesson at one branch between two dates (at most 62 days; default this week), with status and places: the front desk's day view.

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": {
      "branch": "<branch>"
    },
    "name": "list_branch_lessons"
  }
}

Input Schema

Name	Required	Description
`to`	No	To YYYY-MM-DD, in the business's own time zone.
`from`	No	From YYYY-MM-DD, in the business's own time zone.
`branch`	Yes	Branch id or name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds valuable behavioral detail beyond that: the maximum 62-day range, the default to the current week, and that results include status and places.

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?

The description is a single tightly packed sentence with no wasted words. The key scoping and constraint information is front-loaded.

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?

With only three parameters, full schema coverage, and no output schema, the description covers the essential scoping, defaults, and limits. Minor gaps like pagination or ordering are not critical for this list tool.

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 baseline is 3, but the description adds meaning not present in the schema: the 62-day maximum span and the default date range of the current week. It also clarifies that branch scoping is the core filter.

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 resource and scope: every lesson at one branch between two dates, with status and places. It is clear enough to distinguish from a class-specific lesson list, though it does not explicitly name sibling tools like list_class_lessons.

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?

It provides a useful context ('the front desk's day view') and constraints (at most 62 days; default this week), which imply the intended use. However, it does not explicitly say when to use this versus sibling tools such as list_class_lessons or class_history.

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?