Skip to main content
Glama

Bulk purchase numbers

bulk_purchase_numbers
Destructive

Buy several numbers in one area code at once (e.g. for a sender pool). Live numbers are billed monthly each.

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>",
      "quantity": "<quantity>"
    },
    "name": "bulk_purchase_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags to put on the new numbers
pool_idNoAdd the new numbers to this pool
quantityYesHow many numbers to buy (1 to 50)
area_codeYesThree-digit area code to buy in
idempotency_keyNoOptional. Retries are already safe: the same call with the same inputs within 10 minutes is done once and answers with the first result. Pass your own key to dedupe across a longer gap, or a new one to repeat an identical call on purpose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / area_code / description
      Added value: +"Three-digit area code to buy in"
    • addedInput schema / properties / quantity / description
      Added value: +"How many numbers to buy (1 to 50)"
    • addedInput schema / properties / tags / description
      Added value: +"Tags to put on the new numbers"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description adds genuinely non-obvious economics — 'live numbers are billed monthly each' — which annotations cannot convey; annotations instead supply the destructive/openWorld safety profile. It stops short of saying the charge is irreversible, what happens if fewer than `quantity` numbers are available, or that release_number is the undo path.

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?

Two short sentences, scope first then the cost consequence, with no filler. Nearly ideal for a definition this small; a little more rounding-out would still fit without padding.

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?

Schema is fully documented and there is no output schema to explain, so the essentials are covered. For a destructive, money-spending tool it omits what the call returns (the purchased numbers) and failure modes like insufficient balance or inventory.

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 description coverage is 100%, so every parameter including the nuanced idempotency_key retry semantics is already documented in the schema. The description adds no parameter-level meaning (e.g. how tags/pool_id interact with the purchase), 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 (buy) and resource (several numbers) with the scoping constraint 'in one area code at once', which separates it from the single-number sibling. It never names purchase_number explicitly, so the differentiation is implied rather than stated.

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 parenthetical '(e.g. for a sender pool)' implies the intended scenario, so usage is inferable. There is no explicit when-not guidance and no pointer to purchase_number for single buys or to search_available_numbers before committing.

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.