Skip to main content
Glama
OpenInbox – Email for AI Agents

OpenInbox – Email for AI Agents

Official

Read email

read_email
Read-only

Fetch a single email as plain text with detected codes and links, so AI agents can complete signups, logins, and email-flow tests without HTML parsing.

Instructions

Read one email as plain text, with its detected codes and links.

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_idYesAn email_id from list_emails, wait_for_email or get_verification.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful behavioral detail beyond them by stating the body is returned as plain text and that codes and links are detected and surfaced, which tells the agent it can skip manual parsing. It does not say whether the email is marked as read or how missing/invalid ids behave.

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?

One front-loaded sentence that names the operation, the unit of work, and the return shape with no filler. Nothing could be removed without losing information.

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 one-parameter, read-only tool with no output schema, the description covers what the agent gets back (plain text plus extracted codes and links), which is the main thing it needs to decide to call it. Minor omissions are whether the read mutates read-state and what happens on an unknown id.

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% and the single email_id parameter already documents its accepted sources (list_emails, wait_for_email, get_verification). The description adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Read one email') and scopes it to a single message as opposed to a list, which distinguishes it from list_emails. It also previews the return content ('plain text, with its detected codes and links'), though it never names a sibling tool explicitly.

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?

Usage is only implied: an agent infers it should call this once it has an email_id and needs the body, while wait_for_email or list_emails are presumably for obtaining that id. No explicit when-to-use, when-not-to-use, or alternative is stated.

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