Skip to main content
Glama

See Sight Tours

Get request or quote form link

get_quote_link
Read-onlyIdempotent

Use this when a product is booked by request (multi-day trips, private or custom dates) or the traveler wants a quote. Returns the See Sight Tours request form link; the traveler enters contact details and consent there. No payment is taken.

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": {
      "id": "<id>"
    },
    "name": "get_quote_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct id from search_products, e.g. 'tour:<uuid>' or 'trip:<slug>'.
localeNoSite language for links, e.g. 'en' (default) or 'es'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, and the description adds genuinely new behavior: the tool returns a form link, the traveler supplies contact details and consent on that form, and no payment occurs. It does not disclose link expiry, whether links are reusable, or any auth requirements, which keeps it from a 5.

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 short sentences, front-loaded with the usage condition, then the return value, then the downstream flow. No filler and nothing repeated from the schema or annotations.

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?

For a two-parameter read-only link generator with full schema coverage and annotations, the description supplies everything an agent needs: trigger conditions, what is returned, and what happens after the link is handed off. No output schema exists, so the explicit statement of the return value fills that gap well.

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%, with the required id format ('tour:<uuid>', 'trip:<slug>') and the locale enum fully documented in the schema. The description adds nothing about either parameter, so the baseline 3 applies.

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?

States a concrete verb and return value ('Returns the See Sight Tours request form link') plus the exact situation that triggers it (booked by request, multi-day, private/custom dates, or traveler wants a quote). The closing 'No payment is taken' separates it from the payment path represented by create_checkout_session in the sibling set.

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?

Gives explicit when-to-use conditions with concrete examples (multi-day trips, private or custom dates, quote requests) and signals when-not by noting no payment is taken, implying a different tool for paid bookings. It stops short of naming the alternative tool or stating prerequisites such as the product needing request-only booking status.

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