Skip to main content
Glama
Sign In

Conciergr Timetable

by com.conciergr
OverviewDiscussionsAdmin

Remove a trial session

remove_trial_session
Destructive

Remove one trial session (an open house or assessment day).

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>"
    },
    "name": "remove_trial_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe trial session's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered structurally. The description adds nothing beyond that — no mention of permanence, whether attached bookings/seats are released, or whether removal cascades to class history.

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?

A single compact sentence with the verb and resource front-loaded. Efficient, though it has room for one more clause of destructive-behavior context without becoming bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple 1-parameter destructive tool whose annotations and schema cover most of the burden, so this is near-adequate. Still missing the key operational fact an agent needs before calling: what removal actually destroys and whether related trial seats or bookings are affected.

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 a single parameter with 100% schema description coverage, so the schema already documents 'id'. The description adds no format, source, or lookup guidance (e.g. that IDs come from list_trial_sessions), leaving parameter semantics fully to the schema.

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?

States a specific verb and resource ('Remove one trial session') and disambiguates the domain term as an open house or assessment day. It is distinguishable from siblings like remove_class or cancel_lesson by the trial-session scope, though it does not explicitly contrast with them.

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?

No guidance on when to use this versus cancel_lesson or the seat tools (hold_trial_seat/release_trial_seat), nor any prerequisite or warning about when removal is inappropriate. The agent must infer the routing entirely.

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

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