Skip to main content
Glama

Link number to registration

link_number_to_registration
Destructive

Attach a number to an approved 10DLC registration so it can send that registration's traffic.

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": {
      "phone_number": "<phone_number>",
      "registration_id": "<registration_id>"
    },
    "name": "link_number_to_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
phone_numberYesE.164 number you own
registration_idYesThe approved registration to attach the number to (reg_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / registration_id / description
      Added value: +"The approved registration to attach the number to (reg_...)"
  2. First observed

TDQS

A3.5/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 partly covered structurally. The description adds the traffic-routing consequence but explains nothing about the destructive side: whether linking displaces an existing link, whether it can be undone, or what happens on a failed/duplicate link.

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?

One sentence, front-loaded with the action and ending with the outcome. Every clause carries information; nothing is 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?

For a two-parameter mutation flagged destructive with no output schema, the description is minimally adequate: it says what linking accomplishes. It leaves out reversibility, collision behavior with an already-linked number, and any prerequisite checks, which an agent would need before invoking a destructive write.

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 both parameters are fully documented in the schema (E.164 format, reg_... prefix). The description restates the relationship between the two arguments but adds no syntax, format, or constraint detail beyond the schema, 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 and resource ('Attach a number to an approved 10DLC registration') and adds the payoff ('so it can send that registration's traffic'). It is clearly distinct from assign_number_to_customer, though the description never names that or any other sibling to reinforce the distinction.

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?

Implies context via the prerequisites 'approved registration' and (from the schema) a number you own, so the agent can infer eligibility. It gives no explicit when-not guidance, no mention of alternatives like assign_number_to_customer, and no failure conditions.

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.