Skip to main content
Glama

Spoof Caller ID

Prices

get_prices
Read-onlyIdempotent

Per-minute call prices and per-part SMS prices in EUR. Give a country (ISO code like GB) for one country; without it you get a compact list of every country. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNo2-letter ISO country code, e.g. GB, US, DE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 safety is covered. The description adds value beyond that by naming the currency (EUR), stating that the call is free (no billing impact), and sketching the shape of each of the two response modes.

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 short sentences with zero filler: the payload description comes first, then the conditional behavior of the single parameter. Every clause carries information the agent needs.

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

Completeness4/5

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

With one optional parameter, no output schema and full annotation coverage, this is close to complete, and the two result modes plus the currency are disclosed. Minor gaps remain around the exact fields returned per country and whether prices are current or dated, but nothing blocks a correct call.

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 country parameter's type and pattern are already documented, which sets a baseline of 3. The description goes further by making the optionality and the consequence of omission explicit, and by giving a concrete example format (GB), which the schema alone does not spell out.

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?

"Per-minute call prices and per-part SMS prices in EUR" states a specific resource and the two price dimensions clearly, so an agent can tell this apart from siblings like get_balance or hlr_quote that also return monetary values. It lacks an explicit contrast with those siblings, keeping it short of a 5.

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?

The description explains the two invocation modes: pass a country code for one country, omit it for a full list. That is genuine calling guidance, but it addresses parameter usage rather than when to choose this tool over get_balance or hlr_quote, so selection guidance is only implied.

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