Skip to main content
Glama
Sign In
allinbox

allinbox

by tomasbenavidez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

read_email

Read-only

Retrieve one email by ID and strip quoted replies, signatures, and HTML so AI agents get clean message content.

Instructions

Read one email by id. Quoted replies, signatures and HTML are stripped.

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

Input Schema

NameRequiredDescriptionDefault
idYes
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely non-obvious behavioral context — that quoted replies, signatures and HTML are stripped — which tells the agent the returned body is normalized text rather than raw content.

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 short sentences, the core action front-loaded and the content-normalization caveat second. Nothing is wasted or padded.

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 single-record read with annotations and no output schema, the definition covers purpose and content shaping adequately. It falls short on truncation semantics (max_chars) and on how to obtain a valid id, both of which an agent would want before calling.

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 description must carry the param burden. It only glosses 'by id' (the schema pattern already shows the id format) and says nothing at all about max_chars, leaving the default 4000-character truncation behavior completely unexplained.

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 with scope: 'Read one email by id'. The phrase 'one email' implicitly separates it from read_thread, which handles a whole conversation, but no sibling is named 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 by the purpose statement — you must already have an id to call it. There is no guidance on when to prefer read_thread for a full conversation or search_all to find the id in the first place.

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