Skip to main content
Glama

Check eSIM data usage

check-esim-usage
Read-onlyIdempotent

How much data an eSIM has used and how much is left, for one eSIM on a paid order. Identified by the order id and the email that bought it, plus the ICCID from get-order-status or get-esim-activation. Allowances are in megabytes. Readings are served from a cache refreshed every couple of minutes: checked_at says when the reading was taken. An unlimited plan reports its full-speed allowance for the current period rather than a total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesThe email address the order was bought with.
iccidYesThe ICCID of the eSIM to read, as returned by get-order-status.
order_idYesThe order id from the buyer's confirmation email or order page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
iccidYesThe eSIM this reading belongs to.
statusYeseSIM state at the time of the reading, e.g. "active".
checked_atYesWhen this reading was TAKEN, ISO 8601. Readings come from a cache refreshed every couple of minutes, so do not present the number as live.
expires_atYesWhen the plan lapses, ISO 8601. Null when the supplier reports none.
activated_atYesWhen the eSIM first connected, ISO 8601. Null before activation.
data_used_mbYesMegabytes used on the current bundle; 1 GB is 1024 MB.
is_unlimitedYesWhether the plan is sold as unlimited. Almost none are uncapped: see the period fields for what that actually means here.
period_resetYesHow often it refills: "daily", "weekly" or "monthly". Null when it does not.
data_total_mbYesSize of the current bundle in megabytes, reflecting any top-ups. Null on an unmetered plan.
percentage_usedYesShare of the bundle spent, 0-100. Null on an unmetered plan, where there is no total to be a share of.
data_remaining_mbYesMegabytes left. NULL on an unmetered plan, which does not mean zero: it means the supplier reports no allowance to count down.
period_remaining_mbYesFull-speed data left in the CURRENT reset period, for a plan whose allowance refills (say 3 GB a day). Null when the plan has no reset period. Deliberately separate from data_remaining_mb, which describes the whole plan.
percentage_remainingYesShare of the bundle left, 0-100. Null on the same terms.
period_high_speed_mbYesSize of that period allowance, so the figure above can be read as "945 MB of 3 GB left today".
period_reduced_speed_kbpsYesSpeed the plan throttles to once the period allowance is spent. NULL means the data STOPS instead, which is a different thing to tell a traveller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new operational context: readings come from a cache refreshed every couple of minutes, checked_at records when the reading was taken, allowances are in megabytes, and an unlimited plan reports its full-speed allowance rather than a total. This is exactly the kind of behavior an agent cannot infer from structured fields.

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?

Four tight sentences, front-loaded with the core purpose and following with identifier provenance, units, and cache semantics. The opening is telegraphic but every sentence carries information; no padding.

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?

An output schema exists, so return structure need not be described, but the description still supplies units, the checked_at freshness signal, and unlimited-plan semantics — everything an agent needs to interpret and correctly call this read-only 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?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema: it ties email to the buyer of the order, states the ICCID must come from get-order-status or get-esim-activation, and clarifies the three identifiers jointly select one eSIM on a paid order.

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 precise verb+resource (read an eSIM's used/remaining data) and narrows scope to 'one eSIM on a paid order'. No sibling tool covers usage lookup, and the description makes that scope clear without needing the schema.

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

Usage Guidelines4/5

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

Explains that the eSIM must belong to a paid order and where to obtain the ICCID ('from get-order-status or get-esim-activation'), giving real context for correct invocation. It stops short of an explicit when-not-to-use statement or naming a fallback, so it misses the top tier.

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