Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_messages_get_by_id

Get complete message details by providing its ID. Access email or SMS content, headers, and metadata.

Instructions

Retrieve the full detail for a single message by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMessage ID.

Implementation Reference

  • The main implementation of 'mailosaur_messages_get_by_id'. Registers tool with server.tool(), defines schema (id: string), and handler calls mailosaur.messages.getById(id).
    server.tool(
      "mailosaur_messages_get_by_id",
      "Retrieve the full detail for a single message by ID.",
      {
        id: z.string().describe("Message ID.")
      },
      async ({ id }) => {
        const message = await mailosaur.messages.getById(id);
        return response(message);
      }
    );
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits like authentication requirements, rate limits, or side effects (e.g., marking message as read). The description is too sparse to guide the agent on behavioral expectations.

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?

The description is a single sentence that is concise and front-loaded, with no extraneous information. Every word 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?

Given the simplicity of the tool (one required parameter, no output schema), the description is minimally adequate but lacks detail on what 'full detail' includes. It does not compensate for the missing output schema.

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 100% with parameter 'id' documented as 'Message ID.' The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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 'Retrieve', resource 'full detail for a single message', and method 'by ID'. It effectively distinguishes from sibling tools like list (multiple messages) and search (query-based).

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 provides no guidance on when to use this tool versus alternatives, such as when to use list for multiple messages or search for filtering. It lacks explicit when-to-use or when-not-to-use context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MrNewDelhi/mailosaur-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server