Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Update slot reservation

update_slot_reservation

Move a slot reservation to another start time or extend how long it is held.

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>",
      "eventTypeId": "<eventTypeId>",
      "slotStart": "<slotStart>"
    },
    "name": "update_slot_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesReservation uid from reserve_slot.
slotStartYesStart time in ISO 8601, in UTC (e.g. '2026-10-01T09:00:00Z'). Pick it from find_available_slots so it is actually free.
eventTypeIdYesNumeric event type ID, as returned by list_event_types.
slotDurationNoMinutes, for event types with several lengths.
reservationDurationNoMinutes to hold the slot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the mutation profile is covered. The description adds that the mutation targets start time or hold length, but says nothing about what happens to the previous slot, whether the old reservation is released, or failure behavior when the new slot is taken.

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?

A single front-loaded sentence that names the resource first and then enumerates the two capabilities; there is no filler.

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 rich per-parameter schema descriptions, no output schema requirement, and annotations covering the safety profile, the description is nearly sufficient. The remaining gap is operational: what the call returns and how conflicts with the new slot are surfaced.

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 all five parameters are already documented with useful detail (including cross-references to reserve_slot and find_available_slots). The description only loosely maps its two operations onto slotStart and reservationDuration, adding no format or constraint information beyond 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 ('Move a slot reservation') plus the two supported operations (rebooking to a new start time, extending hold duration). It is distinguishable from reserve_slot and release_slot_reservation by scope, though it never names them.

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 'move ... or extend', giving the agent a sense of when the tool applies, but there is no explicit when-not guidance and no mention of the sibling alternatives (reserve_slot to create, release_slot_reservation to discard) that an agent choosing among reservation tools would want.

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

All Caly 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