Skip to main content
Glama

Request short code

request_short_code
Destructive

Ask our team for a short code (or a toll-free number they set up). Provisions nothing by itself; carriers take 8-12 weeks to approve a short code.

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": {
      "type": "<type>",
      "business_name": "<business_name>",
      "monthly_volume": "<monthly_volume>",
      "use_case": "<use_case>"
    },
    "name": "request_short_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesshort_code, or toll_free for a number our team sets up
use_caseYesWhat you will send, in a sentence or two.
business_nameYesThe business the number is for
monthly_volumeYesExpected texts a month

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / business_name / description
      Added value: +"The business the number is for"
    • addedInput schema / properties / monthly_volume / description
      Added value: +"Expected texts a month"
    • addedInput schema / properties / type / description
      Added value: +"short_code, or toll_free for a number our team sets up"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, non-read-only, non-idempotent, but the description usefully qualifies the blast radius: nothing is provisioned, an external approval (carriers, 8-12 weeks) gates the outcome. That is real context beyond the annotation flags. It does not say who is notified, where the request lands, or whether it can be cancelled — gaps for a non-idempotent mutation.

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?

Two tight sentences, zero filler. The core action is front-loaded and the critical constraint (no self-provisioning, long carrier approval) follows immediately.

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?

There is no output schema, so the description must carry the outcome story, and it only half does: it says what will NOT happen (no provisioning) and how long approval takes, but not what the caller receives back or which tool to check status with (list_number_requests / get_registration). For a four-required-field submission with a destructiveHint annotation, that follow-up path is the missing piece.

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% with two enums and per-field descriptions, so the schema already carries parameter meaning. The description only echoes the type split ("short code ... or a toll-free number they set up") and adds no syntax, format, or validation guidance beyond it. Baseline 3 is appropriate.

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?

Specific verb and resource: "Ask our team for a short code (or a toll-free number they set up)" makes clear this is a human-mediated request, distinct from the self-serve purchase_number / search_available_numbers siblings. It stops short of naming any sibling explicitly, so the distinction is inferable 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 phrase "Provisions nothing by itself" implies this is a precursor step rather than the provisioning act, and the 8-12 week note signals the lead time. But there is no explicit when-to-use / when-not-to-use guidance versus purchase_number, bulk_purchase_numbers, or list_number_requests, leaving the agent to infer routing.

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.