Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

Trip Desk Pass: 24 h of every paid tool for one payment ($1.000)

day_pass
Read-only

Use if you will make more than ~7 trip briefs or ~25 other calls in a day. Returns a bearer token valid 24 h (300 successful calls) for every paid tool here: send it as the MCP header Authorization: Bearer , or as the "pass" argument, and you are not charged again. (Also sold for a plain USDC transfer: see payment_options / redeem_transfer_pass; 1 USDC = 24 h, 5 USDC = 7 days.) PAID: $1.000 per call, no API key or account. Pay with x402 over MCP (USDC on Base) or MPP over MCP (USDC.e on Tempo); an unpaid call returns the payment terms and charges nothing. Bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/pass.

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": "day_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior1/5

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

The description says 'PAID: $1.000 per call' and that a successful call returns a bearer token, which is a financial side effect. This directly conflicts with the annotation readOnlyHint=true. Although the description otherwise provides rich payment and failure behavior, the contradiction triggers the rubric's score-1 rule.

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?

The usage threshold and token result are front-loaded, and the remaining pricing/payment details are relevant. It is dense and slightly repetitive on price, but no sentence is clearly wasted for a paid pass tool.

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?

With no output schema, the description still explains the returned token's validity, the 300-call limit, payment methods, unpaid-call behavior, failure non-charge behavior, and alternatives. That is complete for this zero-parameter paid pass tool.

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 has zero input parameters, so the baseline is 4. The description adds useful token-transport semantics for later calls (Authorization header or 'pass' argument), but there are no input parameters to clarify.

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?

The description states a specific outcome: a bearer token valid 24 h for every paid tool, with a concrete usage threshold of more than ~7 trip briefs or ~25 other calls. It also distinguishes this from the plain USDC transfer path by naming payment_options and redeem_transfer_pass.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit 'Use if...' threshold, points to redeem_transfer_pass and payment_options for plain USDC transfers, and explains the unpaid-call fallback. This is clear when-to-use guidance with a named alternative.

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