Skip to main content
Glama

OsmO Travel eSIM

Show data estimate card

show_data_estimate
Read-onlyIdempotent

Shows a trip data estimate as an interactive card.

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": "show_data_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
usageNo
activitiesNo
wifiAtStayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only that the result is an "interactive card," with no information on what the card displays, how defaults are resolved, or how the nested activity inputs affect the estimate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is structurally clean. However, the brevity here is under-specification rather than economy, since no essential detail about inputs or output is present.

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 a required integer, an enum, a boolean, and an eight-field nested object at 0% schema coverage, one sentence is far from enough. The only complete element is that a card is returned; everything an agent needs to fill in the parameters is missing.

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

Parameters1/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 hourly fields and a usage enum. The description mentions none of them, so nothing explains the units, ranges, or interaction between days, usage, activities, and wifiAtStay.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Shows a trip data estimate") and adds that output is an "interactive card," hinting at a presentation role. But it never distinguishes this from the sibling estimate_trip_data, so an agent cannot tell whether this computes or merely renders the estimate.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool such as estimate_trip_data. The agent must infer the selection conditions entirely from the name and the phrase "interactive card."

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