Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

How to pay (free)

payment_options
Read-onlyIdempotent

FREE. Prices, the receiving address and the exact retry format for x402 over MCP (USDC on Base) and MPP over MCP (USDC.e on Tempo), the Trip Desk Pass, and the plain-USDC-transfer option (no x402 client needed: 1 USDC = 24 h, 5 USDC = 7 days), plus the equivalent HTTP endpoints.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "payment_options"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior: it is free, it discloses pricing tiers (1 USDC = 24h, 5 USDC = 7 days), mentions no x402 client is needed for plain transfers, and notes equivalent HTTP endpoints. It does not describe the response format in detail, but for a zero-parameter info tool this is solid.

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

Conciseness4/5

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

Front-loads 'FREE.' and then packs in the useful details. It is a single dense sentence rather than a structured list, which slightly hurts readability, but every clause appears to earn its place.

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 zero-parameter, read-only informational tool with no output schema, the description gives enough detail about what it returns and the payment mechanisms. It could be more explicit that calling it does not initiate a payment, but the read-only annotations make that clear.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify about inputs, and it correctly does not waste words on parameters.

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 specifically that it returns prices, receiving address, retry format, payment options (x402/MPP), Trip Desk Pass, plain-USDC transfer, and HTTP endpoints. The purpose is clear and the contents are enumerated, though the defining verb is implicit rather than stated.

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?

The description implies this is the informational/payment-setup tool, but it never explicitly says when to use it versus action siblings like day_pass or redeem_transfer_pass. The 'FREE' label helps signal it is a lookup, not a purchase, but there is no direct routing guidance.

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