Skip to main content
Glama

Update number pool

update_number_pool
Destructive

Rename a sender pool or change its numbers.

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

Input Schema

NameRequiredDescriptionDefault
idYesPool id
nameNoPool 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

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is known. The description adds nothing about blast radius: it doesn't say whether changing routing affects existing assignments, whether omitted fields are preserved, or what permissions are needed — the key unknowns for a destructive, non-idempotent update.

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?

A single short sentence, front-loaded with the verb and target. It earns brevity, though the second clause wastes space on a capability that does not exist.

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 destructive, non-idempotent mutation with no output schema, the description should state what happens to existing pool numbers and settings when routing or name change. Instead it claims a capability the schema lacks, leaving the agent less informed than the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are documented there, but the description actively misleads by promising number changes that no parameter supports, and it never mentions the routing or description fields. Incorrect signal is worse than no signal here.

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?

Names a specific verb+resource (update a number pool) but the stated scope is partly wrong: the schema exposes id, name, routing and description, with no way to 'change its numbers'. It also doesn't distinguish this from bulk_update_numbers, clone_number_pool, or delete_number_pool.

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 guidance on when to use this instead of bulk_update_numbers (mass changes), clone_number_pool, or delete_number_pool, and no prerequisites or preconditions are mentioned. The agent must infer usage from the name alone.

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.