Skip to main content
Glama

Freedom Agent Mail

read_email

Read one email in full: plain text, codes, links and attachment names.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe inbox token returned by create_inbox.
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose what the response contains, including the notable detail that verification codes and attachment names are surfaced. It does not say whether reading marks the message as read, what happens if message_id is invalid, or that the inbox token from create_inbox is required for authorization.

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?

A single front-loaded sentence with zero filler; the colon construction puts the returned content where an agent will read it first. Every clause carries information.

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?

For a simple two-parameter read tool with no output schema and no annotations, the description covers purpose and returned content adequately. It falls short on message_id semantics and on any failure or side-effect behavior, which an agent needs when a lookup might miss.

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 coverage is only 50%: token is documented in the schema as coming from create_inbox, but message_id has no description anywhere. The phrase "one email" weakly implies message_id identifies a single message, but the description adds no format, provenance, or validation detail to compensate for the undocumented parameter.

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?

"Read one email in full" gives a specific verb and a single-resource scope, and the enumeration of what comes back (plain text, codes, links, attachment names) makes the output concrete. It implicitly separates itself from list_emails by specifying exactly one message and full content, though it never names that sibling.

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?

There is no explicit when-to-use or when-not-to-use statement and no prerequisites. The phrase "one email in full" only implies the workflow (call list_emails or wait_for_email first to obtain a message_id, then read the full body here), so guidance is inferred rather than stated.

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