Skip to main content
Glama

Spoof Caller ID

HLR lookup

hlr_lookup

Live network lookup: is each number active, mobile or landline, which network, ported or not. COSTS MONEY: the price per number with a result is held first; numbers without a result are refunded. Up to 100 numbers per call.

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": {
      "numbers": "<numbers>"
    },
    "name": "hlr_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
numbersYesUp to 100 numbers in international format

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?

Goes well beyond the annotations by disclosing the billing model: price is held per number that returns a result, and numbers with no result are refunded. That is exactly the kind of cost/risk detail an agent needs before invoking. It stops short of a 5 because latency, auth requirements, and what 'no result' looks like are unstated.

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?

Three short sentences, front-loaded with the capability, then the cost warning, then the limit. No filler or redundancy.

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

Completeness5/5

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

With no output schema, the description carries return values itself by listing the fields checked (active, mobile/landline, network, ported). Combined with the billing behavior and the 100-number cap, an agent has everything needed to call it correctly.

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 coverage is 100% and the single array parameter is fully documented (international format, max 100). The description's 'Up to 100 numbers per call' repeats maxItems rather than adding new meaning; the refund-per-number note is the only genuine semantic addition, so the baseline 3 applies.

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?

States a specific verb and resource ('Live network lookup') and enumerates the exact attributes returned: active status, mobile vs landline, network, ported flag. This is far more specific than the title. It does not name hlr_quote, so the distinction between a live (billable) lookup and a price quote is left implicit, keeping it just 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?

Usage is implied by 'Live network lookup' and the cost warning hints that this is the billable step, but there is no explicit statement of when to use this versus hlr_quote (e.g., 'quote first, then look up'). No prerequisites or exclusions are named.

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