Skip to main content
Glama

See Sight Tours

Prepare checkout link

create_checkout_session
Idempotent

Use this when the traveler confirms a quoted departure and wants to book. Returns a short-lived seesight-tours.com link that restores the product, departure, party and currency. Nothing is reserved or charged: the guest reviews the final total and pays on the website. Never ask for card or contact details in chat.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "create_checkout_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesquote_id from check_availability (expires after 15 minutes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only signal non-read-only, non-destructive, idempotent, closed-world), the description discloses what actually matters: nothing is reserved or charged, the link is short-lived, the guest reviews the final total and pays on the website. That is exactly the kind of side-effect and hand-off detail an agent needs and cannot derive from the structured fields.

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 sentences, front-loaded with the triggering condition, then the returned artifact, then the critical no-charge clarification. No redundant restatement of the title or schema, and every sentence carries distinct information.

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

Completeness5/5

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

A single-parameter tool with full schema coverage and no output schema; the description compensates by describing the return value (the link and what it restores) and the no-charge behavior. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100% and the single quote_id is already documented as coming from check_availability with a 15-minute expiry. The description adds only indirect meaning, noting the link restores product, departure, party and currency, which hints at what the quote encodes. Useful but marginal over the schema, 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?

The description makes the action and output concrete: it produces a short-lived seesight-tours.com link that restores the product, departure, party and currency. An agent can tell this is a checkout-link generator rather than an availability or product lookup. It does not explicitly contrast with the sibling get_quote_link, which is the closest name-level confusion risk, so it stops short of a 5.

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?

"Use this when the traveler confirms a quoted departure and wants to book" gives a clear triggering condition, and the closing instruction "Never ask for card or contact details in chat" sets a firm boundary on the conversation flow. It lacks an explicit when-not or a named alternative for pre-confirmation steps, but the context is unambiguous enough to act on.

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