Terudo partner

Payment link

checkout

Creates the payment link for one plan: the traveller pays on the partner's checkout page (checkout_url) and receives the eSIM by e-mail once paid. Give the link to the traveller; nothing is charged until they pay.

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": {
      "plan": "<plan>",
      "email": "<email>"
    },
    "name": "checkout"
  }
}

Input Schema

Name	Required	Description
`plan`	Yes	Plan id, from plans_list or quote_trip.
`trip`	No	Trip dates, so a plan too short is refused.
`email`	Yes	The traveller's e-mail, where the eSIM goes.
`locale`	No	Language of the pay page and e-mails.
`context`	No	Optional: in one sentence, why you are calling this tool for the user. Helps Terudo improve these tools; never shown to anyone else.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already flag a non-read-only, non-destructive, non-idempotent operation, and the description adds real value by clarifying no money is captured at call time and that delivery happens after payment. However, for a non-idempotent mutation it omits the key operational facts: whether repeated calls mint duplicate links, link expiry/lifetime, and any auth or partner-account prerequisite.

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?

Two compact sentences, front-loaded with what is created and what the agent must do with it, with zero filler. The 'nothing is charged until they pay' clause earns its place as a decision-relevant fact.

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?

Covers the essentials for a five-parameter creation tool with a nested trip object and no output schema: it names the URL field the caller gets back and the fulfilment path. It falls short only on link lifetime, repeat-call behavior, and failure modes when the trip dates conflict with the plan.

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 description coverage is 100%, so the baseline is 3; the schema itself explains plan provenance, trip-date validation, email destination, and locale. The description adds only 'for one plan' (one link per plan) and does not elaborate on trip-dates validation or the context field.

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 a specific verb and resource ('Creates the payment link for one plan') and names the returned artifact (checkout_url) plus the downstream consequence (traveller receives the eSIM by e-mail). It does not differentiate itself from siblings such as quote_trip or esim_page, so an agent must infer the routing boundary.

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?

Implies usage (traveller is ready to buy; give them the link) and clarifies that no charge occurs until payment, which is useful pre-call context. It never states when to prefer this over quote_trip/plans_list or what preconditions must be satisfied, leaving selection to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Terudo partner tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?