Skip to main content
Glama

Estimate mobile data for a trip

estimate_trip_data
Read-onlyIdempotent

How much mobile data a trip needs, and the plan size to pick, for light, typical or heavy use.

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": {
      "days": "<days>"
    },
    "name": "estimate_trip_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesTrip length in days (1-365).
profileNolight: maps and messaging; typical: plus social, music, a little video; heavy: HD video, hotspot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety profile is covered. The description adds the useful hint that the result includes a plan-size recommendation, but says nothing about accuracy assumptions, units, or how the estimate is derived — modest added value over the annotations.

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?

One sentence, front-loaded with the core output, with zero filler. It is a noun-phrase fragment rather than a verb-led statement, which slightly reduces crispness but avoids padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two simple parameters the input side is fully covered, but there is no output schema, and the description never indicates what the return value looks like (a data amount in GB/MB, a plan tier, or both). For a tool whose entire purpose is producing a number and a recommendation, that omission leaves a real gap.

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%, with both parameters documented and the profile enum fully explained in the schema itself. The description's mention of 'light, typical or heavy use' merely restates the enum, adding no syntax, defaults, or edge-case behavior beyond structured data.

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?

The description names a specific computation (mobile data needed for a trip) plus a second output (recommended plan size) and the three use profiles. It is clear enough to distinguish from sibling plan-listing tools, but it never explicitly names an alternative, so differentiation is inferred from the resource rather than stated.

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?

Usage is only implied: an agent can infer this is a pre-trip estimation step, presumably before find_esim_plans. There is no explicit when-to-use, when-not-to-use, or statement of prerequisites, and no pointer to siblings.

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