Skip to main content
Glama

OsmO Travel eSIM

Estimate trip data

estimate_trip_data
Read-onlyIdempotent

Use this when the user is unsure how much mobile data they need for a trip. Returns an estimate with its assumptions and sources.

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
daysYes
usageNo
activitiesNo
wifiAtStayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds value beyond them by disclosing what the response contains: an estimate together with its assumptions and sources, which matters because there is no output schema. It says nothing about accuracy bounds or how the estimate is derived, which would have pushed this higher.

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 sentences, both front-loaded: the trigger first, then the return shape. There is no filler, hedging, or repeated information.

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

Completeness2/5

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

For a tool with four parameters, one nested object, an enum, and zero schema description coverage, the definition is thin: an agent knows when to call it and roughly what comes back, but not what the activity fields mean, whether activities override the usage preset, or how defaults behave. The added note about assumptions and sources partly compensates for the missing output schema but not for the undocumented inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, including a nested activities object with eight hour/minute fields, so the description is the only place semantics could be supplied. It mentions none of them: not days, not the light/moderate/heavy usage enum, not wifiAtStay, and not how activity hours interact with the usage preset. The 'trip' framing hints at a duration input but adds no usable meaning.

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 states a specific verb and resource: it returns an estimate of how much mobile data a trip needs, with assumptions and sources. That is clearly more than a restatement of the name. It does not, however, distinguish this from the sibling show_data_estimate, so an agent must infer the split from names alone.

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?

'Use this when the user is unsure how much mobile data they need for a trip' gives a concrete trigger condition rather than a generic 'use for estimates'. There are no exclusions, prerequisites, or named alternatives, and the presence of show_data_estimate makes the absence of routing guidance a real, if minor, gap.

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