Skip to main content
Glama

Little Works

get_booking_confirm_link

Claim / confirm URL for a booking id.

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": {
      "bookingId": "<bookingId>"
    },
    "name": "get_booking_confirm_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It does not say whether 'Claim' mutates booking state, whether the returned URL is single-use or expiring, whether authentication or ownership is required, or whether repeated calls return the same link — all material for a tool with a potentially stateful verb.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted words, so it is efficiently sized, but it is telegraphic and under-specified rather than crisp. The 'Claim / confirm' phrasing introduces ambiguity instead of front-loading a clear action.

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?

For a tool with no annotations, no output schema, and an undocumented parameter, the description is too thin — it never states what the return value looks like (a URL string, an object) or the side effects of claiming. An agent could call it, but not confidently predict the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate, and it only restates that the input is a booking id — which the parameter name bookingId already conveys. It adds no format, source, or constraint (e.g. where to obtain a valid id) beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb-resource pair ('Claim / confirm URL') scoped to a booking id, so an agent can guess it returns a confirmation/claim link. However, the slash-alternative and the word 'Claim' leave ambiguity about whether it retrieves an existing link or mints/claims one, and it never distinguishes itself from nearby retrieval tools like get_booking_slots or get_public_share_url.

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?

There is no guidance on when to call this versus other booking tools such as get_booking_slots or create_booking, nor any stated precondition (e.g. booking must exist, must be confirmed, must belong to the caller). The agent must infer usage entirely from the name.

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.

Resources