Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Get booking history

get_booking_history
Read-onlyIdempotent

Show the audit trail of changes made to a booking: who changed what, and when.

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": {
      "bookingUid": "<bookingUid>"
    },
    "name": "get_booking_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookingUidYesBooking UID (a string like '2NtaeaVcKfpmSZ4CthFdfk'), as returned by list_bookings or create_booking.

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, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful return-content context (actor, change, timestamp) that the annotations do not provide, but says nothing about ordering, pagination, or retention of the trail.

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 sentence with zero filler, and the key concept (audit trail of changes) is front-loaded before the clarifying 'who/what/when' detail.

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 read-only, single-parameter lookup with full schema coverage and complete annotations, the description supplies the one thing structured data lacks: what the returned history contains. Only ordering/pagination details are missing, which is minor here.

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?

Only one parameter, and the schema documents it at 100% coverage including the expected UID format and where to obtain it. The description adds nothing about bookingUid, so the baseline 3 applies.

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: showing the audit trail of changes to a booking, further specified as 'who changed what, and when'. This clearly distinguishes it from get_booking (current state) even though no sibling is named explicitly.

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 the word 'audit trail' — an agent can infer this is for change history rather than the booking's current state — but there is no explicit 'use this when...' or exclusion pointing to get_booking for current details.

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