joltsms-mcp-server

joltsms_get_number

Fetch complete details for one phone number, including service label, tags, notes, message counts, billing dates, and subscription status. Accept a UUID or phone number as input.

Instructions

Get full details for a single phone number, including service label, tags, notes, message counts, billing dates, and subscription status.

Accepts a UUID or phone number (e.g. "+16505551234", "650-555-1234", "(650) 555-1234").

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

Input Schema

Name	Required	Description	Default
`number_id`	Yes	Number ID (UUID) or phone number (e.g. +17243213654 or 7243213654)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 16, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the response content (the fields it returns), which is useful, but says nothing about permissions, error behavior for a non-existent number, rate limits, or whether the lookup is scoped to the account.

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?

Two sentences, front-loaded with the action and result set, then the accepted input formats. The field enumeration is slightly long but each item tells the agent what it will receive, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by listing the returned fields, which is exactly what an agent needs to decide whether to call it. The remaining gap is behavioral (auth/error handling) rather than structural.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema's single example by listing accepted input shapes: UUID, E.164 ('+16505551234'), dashed ('650-555-1234'), and parenthesized ('(650) 555-1234'). This tells the agent the lookup tolerates human-formatted numbers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('a single phone number') and enumerates the exact payload (service label, tags, notes, message counts, billing dates, subscription status). This clearly separates it from the list/update/provision siblings without needing to name them.

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?

Usage is only implied: the word 'single' hints that this is the per-number lookup counterpart to joltsms_list_numbers, but no explicit when-to-use, when-not, or alternative is given. No prerequisites or conditions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server