Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

get_message_status

Retrieve the delivery status of a sent SMS by message ID or external ID, including timestamps, error message, and machine-readable error code.

Instructions

Get delivery status of a sent message (queued, sent, delivered, failed, expired) with timestamps, errorMessage and machine-readable errorCode (expired, undelivered, rejected, deleted, unknown, repeated_failure, not_sent), by message id or external id.

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

Input Schema

NameRequiredDescriptionDefault
idYesMessage id or externalId returned when sending.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full disclosure burden and does most of it: it lists returned fields (timestamps, errorMessage, errorCode) and the full enumerations of statuses and error codes. It does not explicitly confirm the call is a non-mutating read or discuss rate limits, which keeps it from a 5.

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?

One sentence, front-loaded with the action and resource, with enum values in parentheticals rather than prose. The dense double enumeration of statuses and error codes is information-bearing but borders on cramped.

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 single-parameter read with no output schema, the description supplies the response shape an agent needs (statuses, timestamps, error fields and codes). Only the non-mutating nature and terminal-state behavior are left implicit.

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 the single parameter is already documented as 'Message id or externalId returned when sending'. The description's 'by message id or external id' merely restates that, adding no format, length or resolution-order detail.

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'), a specific resource ('delivery status of a sent message'), and enumerates the possible status values, so an agent can tell it apart from siblings like get_bulk_job without opening a schema.

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: check status after sending, keyed by 'message id or external id'. There is no explicit when-to-use vs alternatives, no note on when status is terminal (e.g. expired, failed) and no prerequisites stated.

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