joltsms-mcp-server

joltsms_billing_status

Check billing and subscription status for JoltSMS numbers, showing health, price, renewal or cancellation dates, auto-renew, and matching phone numbers.

Instructions

Check billing and subscription status for all your JoltSMS numbers.

Shows each subscription with billing health, price, renewal/cancellation dates, and auto-renew status. Cross-references with phone numbers for easy identification.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "joltsms_billing_status"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max subscriptions to show (1-10, default 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 16, 2026

TDQS

B3.4/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 behavioral burden. It usefully enumerates the return fields (billing health, price, renewal/cancellation dates, auto-renew status), but does not disclose read-only nature, auth requirements, pagination, or that the 'all your numbers' claim is capped by the limit parameter (max 10).

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?

Three sentences, front-loaded with the purpose, then return details and identification context. Every sentence earns its place with no redundancy.

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?

For a simple read-only status tool with one optional parameter, the description explains what is returned, compensating for the missing output schema. However, it does not reconcile the 'all' scope with the 1–10 limit, leaving a small completeness gap.

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?

The single optional limit parameter is fully described in the schema (100% coverage), so the baseline of 3 applies. The description adds no syntax or meaning beyond the schema, and its 'all your numbers' phrasing slightly conflicts with the limit cap.

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 'Check' and resource 'billing and subscription status' scoped to JoltSMS numbers. It implies a distinct resource from sibling number-management tools, though it does not explicitly name an alternative, so it falls just short of full sibling differentiation.

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?

Gives no when-to-use guidance, prerequisites, or alternatives. An agent must infer from the purpose alone that this is the tool for billing status, with no exclusions stated.

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

Deploy Server