Skip to main content
Glama

Trip Desk: visa, travel advisories and trip briefs

Redeem a plain USDC transfer for a Trip Desk Pass (free)

redeem_transfer_pass
Read-onlyIdempotent

FREE. After sending at least 1 USDC (24 h, 300 calls) or 5 USDC (7 days, 2,100 calls) on Base to this server's receiving address from any wallet (see payment_options), pass the transaction hash here and get the bearer token for every paid tool. Redeeming the same tx again returns the same token. Not for x402 payments.

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": {
      "tx": "<tx>"
    },
    "name": "redeem_transfer_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYes0x-prefixed hash of your USDC transfer on Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description still adds concrete value by naming the return value (a bearer token unlocking every paid tool) and the quota attached to each tier. The idempotency sentence largely restates idempotentHint=true, though it makes the 'same token' outcome explicit rather than implied.

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 the decisive fact ('FREE') and every clause carries information (tiers, address source, return value, exclusion). The main sentence is long and parenthesis-heavy, which makes it slightly harder to scan than it could be, but nothing is wasted.

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 one-parameter tool with no output schema, the description supplies what the schema cannot: the prerequisite transfer, the qualifying tiers, the returned bearer token, and how other paid tools should use it. An agent has everything needed to invoke it correctly on the first attempt.

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?

Schema coverage is 100% and the single parameter is already documented as a 0x-prefixed Base transfer hash. The description still adds constraint meaning the schema lacks — which transfers qualify (minimum 1 or 5 USDC, on Base, from any wallet) — so it earns slightly above the baseline-3.

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 specific verb and resource — redeem a Base USDC transfer tx hash for a bearer token — plus the exact access tiers (1 USDC/24h/300 calls, 5 USDC/7 days/2,100 calls). It explicitly excludes x402 payments and points to payment_options, so it is distinguishable from siblings without opening any schema.

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?

Gives the full precondition chain: send USDC on Base to the server's receiving address from any wallet, see payment_options for the address, then submit the hash. It also states the exclusion ('Not for x402 payments') and the repeat-use case, which is exactly the when/when-not guidance an agent needs.

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