Skip to main content
Glama

OsmO Travel eSIM

Show device check card

show_device_check
Read-onlyIdempotent

Shows whether a phone supports eSIM 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": {
      "deviceModel": "<deviceModel>"
    },
    "name": "show_device_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceModelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only the notable behavioral detail that the result is presented as an interactive card rather than structured data, but it says nothing about what happens for unsupported or unrecognized models.

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 short front-loaded sentence with no filler. It is efficient, though the brevity is partly the cause of the missing parameter and usage detail rather than a sign of completeness.

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?

For a single-parameter read-only tool with no output schema, the definition is close to adequate: the card rendering is disclosed and annotations cover safety. The unexplained deviceModel format and the lack of differentiation from check_esim_device leave real gaps an agent would hit in practice.

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% for the single required parameter deviceModel, so the description must carry that meaning and does not. It never says whether deviceModel is a marketing name, a model code, or something else, despite the 2-80 character constraint implying free-form input.

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 gives a specific verb ("Shows") and a specific subject (eSIM support for a phone) plus the delivery form ("interactive card"). It is clear what the tool does, but it never distinguishes itself from the sibling check_esim_device, which by name appears to cover the same question in a different form.

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 exclusions, and no named alternative. An agent facing both show_device_check and check_esim_device gets no signal about which to pick, even though the word "card" hints at a UI-rendering variant rather than a raw data lookup.

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