Skip to main content
Glama

MeiSIM USA

Search US phone-number plans

search_us_numbers
Read-only

Find real US phone-number plans (a genuine US carrier line with calls, texts, and data, no SSN or contract). Use this when the user wants an actual US number, not just travel data. Returns a plan_id for purchase.

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

Input Schema

NameRequiredDescriptionDefault
max_price_usdNoOptional max monthly price in USD.

Output Schema

NameRequiredDescriptionDefault
metaYes
plansYes
how_to_buyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the description's added value is the domain constraints: no SSN and no contract required, plus the fact that a plan_id is returned for a follow-up purchase. That hand-off hint is behaviorally useful beyond the schema and annotations. It says nothing about how many plans come back or whether results vary by availability, but the output schema covers the return shape.

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 tight sentences: the capability and its defining constraints come first, then the selection rule and the returned identifier. No filler or redundant restatement of the name.

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 annotations covering safety, a full schema description, and an output schema, the description supplies what structured fields cannot: what "real" means here and that plan_id feeds a purchase step. The only missing piece is any hint that the optional price filter exists, which is minor for a one-parameter tool.

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?

Only one parameter exists and the schema documents it fully ("Optional max monthly price in USD"), so the baseline is 3. The description does not mention that results can be filtered by budget, meaning an agent could overlook the price filter entirely from the description alone.

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?

"Find real US phone-number plans" gives a specific verb and resource, and the parenthetical defines the offering (carrier line with calls, texts, data, no SSN or contract). The phrase "not just travel data" implicitly separates it from a travel-plan sibling, though it never names that sibling, so differentiation is suggestive rather than explicit.

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 wants an actual US number, not just travel data" supplies a clear selection condition plus an implicit exclusion. It stops short of naming the alternative tool to route to, so an agent must infer which sibling serves the travel-data case.

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.