Skip to main content
Glama

read_email

Retrieves the full text of a single email by its ID so an AI accounts-payable clerk can inspect message content and act on invoice or vendor details.

Instructions

Full text of one email.

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": {
      "email_id": "<email_id>"
    },
    "name": "read_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full behavioral burden. It implies a read operation by saying 'Full text' but does not state that it is read-only, whether it marks the email as read, what permissions are required, or how missing emails are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short phrase with no wasted words, but it is under-specified rather than appropriately concise. It is front-loaded only in the sense that there is nothing else to follow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one required parameter, no annotations, and no output schema, the description is incomplete. It does not explain email_id semantics, whether the full text includes headers or attachments, or what happens on invalid IDs.

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?

Schema description coverage is 0%, so the single email_id parameter is undocumented in the schema. The description only implies that it identifies 'one email' and adds no format, source, or constraint details to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Full text of one email' identifies the resource and suggests the return payload, but it omits an explicit verb such as retrieve or read. It is distinguishable from list_inbox and send_email, yet remains a fragment rather than a complete purpose statement.

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 guidance on when to use this tool versus list_inbox, send_email, or other siblings. There are no prerequisites, exclusions, or conditions for selecting this tool.

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