Skip to main content
Glama
Sign In
@aiwerk/mcp-server-cal

@aiwerk/mcp-server-cal

Official
by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

cal_reschedule_booking

Reschedule an existing booking to a new time using the booking ID and new start date in ISO 8601 format. Optionally include a reason for the change.

Instructions

Reschedule a booking to a new time. Required: uid, newStart (ISO 8601). Optional: reschedulingReason.

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": {
      "uid": "<uid>",
      "newStart": "<newStart>"
    },
    "name": "cal_reschedule_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
newStartYes
reschedulingReasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'reschedule a booking to a new time' without detailing side effects (e.g., old slot availability, confirmation, permissions) or prerequisites.

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 very concise with two sentences, front-loading the action and resource. No wasted words.

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

Completeness2/5

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

The description lacks information about return values, error conditions, or constraints (e.g., only future times). With no output schema, the agent is left uninformed about the outcome of the tool call.

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?

The schema has 0% description coverage, but the description adds meaning by specifying the format (ISO 8601 for newStart) and which parameters are required vs optional. For 3 parameters, this provides useful guidance beyond the raw schema.

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 clearly states the action (Reschedule) and resource (booking). It distinguishes from sibling tools like cal_create_booking (create) and cal_cancel_booking (cancel), so the agent knows when to use this tool.

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

Usage Guidelines4/5

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

The description lists required and optional parameters explicitly, providing clear usage instructions. It does not explicitly state when to use this tool vs alternatives, but the tool name and purpose are sufficiently distinct.

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

Deploy Server

Other Tools