Skip to main content
Glama

Create number pool

create_number_pool
Destructive

Create a sender pool from numbers you own.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPool name
routingNoHow a recipient gets a number. sticky: the same member every time. local: a member in the recipient's area code, else one in their time zone, else any; still the same one each time.sticky
descriptionNoWhat the pool is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"What the pool is for"
    • addedInput schema / properties / name / description
      Added value: +"Pool name"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false), so the safety burden is partly carried. The description adds only the 'numbers you own' precondition and says nothing about whether the pool starts empty, how numbers join it, or why a create is flagged destructive — a genuine gap the annotations can't fill.

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?

One front-loaded sentence with zero filler, and the action is stated first. It is arguably undersized rather than bloated, so conciseness itself is fine; the missing content is scored under other dimensions.

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?

For a 3-parameter create tool with a fully documented schema and no output schema, the definition is minimally sufficient to pick and call it. It omits the post-creation state (empty pool, numbers added later via update_number_pool) and the rationale behind destructiveHint=true, leaving an agent without a mental model of the result.

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% and the routing enum is fully self-explained in the schema, so the description correctly defers. It adds no meaning beyond the schema — notably it never clarifies that no numbers are supplied at creation time, which is the one thing an agent might misread the schema on.

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?

A specific verb + resource ('Create a sender pool'), which is unambiguous next to siblings like clone_number_pool, update_number_pool, and delete_number_pool. Minor terminology drift: the description says 'sender pool' while the name, title, and all siblings say 'number pool', though the synonymy is obvious enough not to confuse.

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?

'from numbers you own' implies the prerequisite that numbers must already be purchased, which is the main gating condition. But there is no explicit when-to-use/when-not guidance and no routing to clone_number_pool (duplicate an existing config) or update_number_pool (change routing afterwards), which are the natural alternatives an agent would weigh.

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.