Skip to main content
Glama
Sign In

Terudo partner

by com.terudo
OverviewDiscussionsAdmin

Server Details

Travel eSIMs for travel businesses: quotes, phone and plan checks, orders, top-ups, webhooks.

Ownership verified
Status
Healthy
Uptime
82.6% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target clearly different stages: destinations, plans_list, compatibility_check, coverage_check, quote_trip, checkout, esim_page, plus the meta get_more_tools. The only real overlap is plans_list vs quote_trip, both returning plans, but the descriptions distinguish 'all plans with from-prices' from 'the recommended plan for a trip'. get_more_tools is clearly marked as a non-domain escape hatch, so it should not be confused with a real action.

Naming Consistency3/5

Everything is snake_case, which helps, but the word order is mixed: noun_verb (compatibility_check, coverage_check, plans_list), verb_noun (get_more_tools, quote_trip), and bare nouns (checkout, destinations, esim_page). Readable and memorable, but there is no single predictable pattern an agent could generalise from.

Tool Count5/5

Eight tools is a well-scoped set for an eSIM resale flow: discovery, two pre-sale checks, quoting, checkout, and post-sale page access. Each tool covers a distinct step and none looks like filler, so the surface is neither thin nor bloated.

Completeness3/5

The pre-sale side is strong (destinations, plans, quote, compatibility, coverage, checkout link) and esim_page covers post-install data. But there is a dead end between paying and getting the eSIM page: no tool to confirm an order or payment status, no order/customer lookup, and no cancellation, refund, or top-up operation. The esim_id coming only from the traveller's e-mail link makes the lifecycle only partly self-service.

Available Tools

8 tools
checkoutPayment linkAInspect

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.

Inputs: plan (required), email (required), trip, locale, +1 more.

compatibility_checkCheck phone compatibilityA
Read-onlyIdempotent
Inspect

Whether the traveller's phone takes an eSIM, from its model name: yes, depends, no or unknown, with a note and the two checks to do on the phone (dial *#06# for an EID, phone not carrier-locked).

Inputs: device (required), context.

coverage_checkCheck French plan coverageA
Read-onlyIdempotent
Inspect

Whether the traveller's French mobile plan already covers the destination (verified records of the main French plans), with advice. Ask before selling: the honest answer is sometimes that no eSIM is needed.

Inputs: destination (required), plan, brand, context.

destinationsDestinationsC
Read-onlyIdempotent
Inspect

Every destination sold, with its name in French and English.

Inputs: context.

esim_pageTraveller's eSIMA
Read-onlyIdempotent
Inspect

The traveller's eSIM page as data (status, install steps, data left), from the eSIM id in their e-mail link.

Inputs: id (required), context.

get_more_toolsAInspect

Report that the user's request needs a capability this server does not have. Records the report for the server's developers; it does not return or add tools.

Inputs: context (required).

plans_listList plansA
Read-onlyIdempotent
Inspect

Plans with their public price (price_cents, TTC). Give a destination for its plans, and days to also get daily plans sized for that stay. Without a destination: every fixed plan, for 'from' prices.

Inputs: days, context, destination.

quote_tripQuote a tripB
Idempotent
Inspect

The plans that cover a trip, with the recommended one: the cheapest covering the trip days plus a buffer day. Nothing is created.

Inputs: end_date (required), start_date (required), destination (required), context, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    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