Skip to main content
Glama
Sign In
Missive MCP

Missive MCP

by kanjidoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

missive_get_message

Read-only

Retrieve message details by ID, including headers, body, attachments, and parent conversation. Supports batch-fetching multiple messages in one call.

Instructions

Fetch one or more Missive messages (headers, body, attachments, and parent conversation) by message id. Pass one id for a single message or several ids to batch-fetch them in one call. Read-only.

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_ids": "<message_ids>"
    },
    "name": "missive_get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idsYesOne or more message IDs to fetch. Multiple IDs are batched into a single request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The description adds context beyond the readOnlyHint annotation by specifying exactly what data is fetched (headers, body, attachments, parent conversation). This aligns with and supplements the annotation.

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?

Two sentences, front-loaded with the core purpose. Every word is valuable, and the structure is optimal.

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 one-parameter read-only tool, the description covers purpose, parameter usage, and content returned. While no output schema, the description is sufficiently complete.

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?

With 100% schema description coverage, the description adds no new meaning beyond the schema. The baseline of 3 is appropriate as the schema already documents the parameter clearly.

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?

The description clearly states the verb 'Fetch' and the resource 'Missive messages' with specific details (headers, body, attachments, parent conversation). It also mentions batch fetching, distinguishing it from listing tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: pass one id for single message or several ids for batch. While it doesn't explicitly state when not to use, the context is clear enough given the sibling tools.

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

Deploy Server

Other Tools