Skip to main content
Glama

Inspect outreach message

spur_get_outreach_message
Read-onlyIdempotent

Read a sent message's body, delivery details and response context.

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

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered without the description. The text adds that the message is a sent message (not a draft or template) and enumerates the returning content, but says nothing about what happens with an unknown or draft message_id, or about any permission requirements.

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?

A single front-loaded sentence with the verb and resource up front and no filler. Slightly terse given the remaining gaps, but nothing is wasted.

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 does list the return contents, which is appropriate for a simple single-parameter read tool. However, it leaves the ID's origin and failure behavior unspecified, so an agent can identify the tool but not fully anticipate its inputs and errors.

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

Parameters2/5

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

There is one parameter and schema description coverage is 0%, so the description must carry the meaning. It only implies via 'a sent message's' that message_id identifies a sent message rather than a draft, template, or campaign, and supplies no format, source, or retrieval guidance for the 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 (read) plus resource (a sent message) plus the payload it returns (body, delivery details, response context). It clearly reads rather than mutates, distinguishing it from siblings like spur_draft_message or spur_delete_message_template, though it does not explicitly contrast with look-alikes such as spur_get_outreach_report or spur_get_sms_conversation.

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?

The description gives no when-to-use guidance, no prerequisites, and does not name an alternative tool or the condition under which another sibling (e.g., the outreach report or SMS conversation tools) should be preferred. The agent must infer from the name alone that this is the per-message drill-down.

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.

Resources