Skip to main content
Glama

reschedule_session

Move a session to a new time (confirm-gated). newStart/newEnd are ISO date-time strings. Both client and coach are notified by the existing flow.

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": {
      "sessionId": "<sessionId>",
      "newStart": "<newStart>",
      "newEnd": "<newEnd>"
    },
    "name": "reschedule_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
newEndYesISO date-time
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
newStartYesISO date-time
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safety profile (non-destructive write, closed-world), and the description adds real context beyond them: the operation is confirm-gated and both client and coach receive notifications through the existing flow. That side-effect disclosure is exactly the kind of behavioral detail an agent needs before mutating a booking; only conflict handling is unstated.

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?

Three short sentences, front-loaded with the action and the gating behavior, followed by parameter format and side effects. No sentence is redundant or padded.

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 four-parameter mutation tool with no output schema, the description covers the action, the confirm gate, and notification side effects. What is left out — preview payload contents and conflict/availability behavior — is minor and partly recoverable from the schema's confirm description.

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?

With 75% schema coverage, the schema already documents newStart, newEnd and confirm including the preview semantics. The description only restates that newStart/newEnd are ISO date-time strings, adding no formatting example, timezone rule, or sessionId meaning. Baseline 3 fits since structured fields are doing the work.

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 verb and resource ('Move a session to a new time') and adds the gating qualifier '(confirm-gated)', which separates it from scheduling and cancellation siblings. It stops short of naming an alternative tool, so an agent must infer that this is the mutation counterpart to cancel_session/schedule_session.

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?

Usage is implied by 'confirm-gated' and the preview-then-execute pattern, which tells the agent it must call twice or pass confirm=true. There is no explicit statement of when to prefer this over cancel-and-rebook, nor any prerequisite about session state (e.g. must be not-yet-completed).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.