Skip to main content
Glama

message_status

Read-only

Read the recorded outcome for a message ID to verify delivery and detect uncertain sending records left by a crash, preventing resend under a new ID.

Instructions

Read the recorded outcome for one message ID. A sending record left after a crash is uncertain and must not be resent under a new 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": {
      "message_id": "<message_id>"
    },
    "name": "message_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful operational context beyond that: a record left after a crash is uncertain and the caller must not resend under a new ID. It does not say what happens for an unknown or expired message ID, leaving one behavioral gap.

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 purpose and zero filler. The second sentence is terse to the point of being slightly cryptic ('must not be resent under a new ID'), but it earns its place.

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?

With no output schema, the description carries the burden of explaining what 'recorded outcome' looks like, yet it never names possible status values or the response for an unknown ID. For a single-parameter read with annotations supplied, this is adequate but leaves a real 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?

Schema description coverage is 0% and the single message_id parameter has no format, origin, or length guidance in the description. The crash sentence implies the ID is the one originally used to send, which adds some meaning, but the caller still cannot tell where to obtain a valid ID.

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+resource: 'Read the recorded outcome for one message ID', with the singular scope ('one message ID') implicitly distinguishing it from the plural sibling read_messages. It stops short of naming an alternative explicitly, so it is clear but not fully self-differentiating.

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 crash/uncertain-send sentence strongly implies the intended scenario (checking outcome before retrying), but the guidance is framed as a warning rather than a when-to-use rule. No explicit exclusions or direct naming of send_message/read_messages as alternatives.

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