Skip to main content
Glama

Clone number pool

clone_number_pool
Destructive

Copy a sender pool under a new name.

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

Input Schema

NameRequiredDescriptionDefault
idYesPool id
nameNoName of the new pool

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"Name of the new pool"
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds the meaningful detail that this produces a distinct new pool rather than renaming the original, but says nothing about what is carried over (numbers, settings, webhooks) or whether repeated calls create duplicate clones.

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?

A single front-loaded sentence with the operation and its distinguishing qualifier. No filler, nothing buried.

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 two-parameter clone tool with full schema coverage and annotations, this is adequate but thin. An agent still cannot tell what the clone inherits, whether the copy is immediately usable, or what identifying information comes back, which matters for a mutation tool with no output schema.

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% with both parameters documented, so baseline is 3. The phrase 'under a new name' lightly reinforces that 'name' labels the clone rather than the source, but adds no format, uniqueness, or defaulting rules beyond the schema.

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 (copy/clone) and resource (sender pool) plus the key outcome (a new pool under a new name). It implicitly separates itself from create_number_pool (creates from scratch) and update_number_pool (mutates in place), though it never names those siblings explicitly.

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?

No when-to-use or when-not-to-use guidance. With create_number_pool, update_number_pool, get_number_pool, delete_number_pool and list_number_pools all present, the agent gets no help deciding between cloning, creating, or editing a pool.

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.