Skip to main content
Glama

Find phone numbers to buy

search_numbers
Read-only

Available US numbers by area code, for the crew's lines.

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": {
      "area_code": "<area_code>"
    },
    "name": "search_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
area_codeYes3-digit area code, e.g. 801.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only 'available' (not already taken) and the opaque phrase 'for the crew's lines', which communicates nothing actionable about result volume, ordering, or what an empty result means.

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?

It is short with no padding, but it is a single noun-phrase fragment rather than a front-loaded statement of action. 'For the crew's lines' occupies space without conveying information.

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 simple one-parameter read tool with annotations this could be near-complete, but the missing hand-off to buy_number leaves the agent without the next step. Nothing explains what the returned numbers look like or whether they can be reserved.

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 schema already documents the 3-digit area code with an example. The description adds only the US-only scoping and the 'available' qualifier, so baseline 3 applies.

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 fragment names the resource (US phone numbers) and the filter (by area code), so an agent can infer it searches availability. But there is no verb and no mention of the obvious sibling buy_number, so the boundary between searching and purchasing is left to inference.

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 and no mention of buy_number, accept_outbound_agreement, or any prerequisite for acquiring a number. The agent must guess whether this tool merely lists candidates or is the acquisition step.

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.