Skip to main content
Glama

Hail Communication for AI

Get an email

get_email
Read-onlyIdempotent

Read a complete workspace email by ID.

    Returns ``body_text``, ``body_html`` and other email fields.
    Inbound records include reply headers and spam, virus, SPF, DKIM and DMARC verdicts.
    Attachments include IDs and file metadata.
    An unknown or inaccessible email returns an error.

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": "get_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesEmail ID, from ``send_email`` or ``list_emails``.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: inbound records carry reply headers plus spam, virus, SPF, DKIM and DMARC verdicts, attachments expose IDs and file metadata, and inaccessible IDs fail with an error — all useful for interpreting results and handling failures.

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

Conciseness4/5

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

Four short sentences, front-loaded with the core action and followed by return contents, edge-case payloads, and failure behavior. Slight overlap with the output schema in enumerating returned fields, but nothing is wasted or buried.

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

Completeness5/5

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

For a single-record read tool with full annotation coverage, a documented schema, and an output schema, the description supplies everything else an agent needs: error behavior on unknown IDs and the shape of inbound and attachment payloads. No material gap remains.

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 coverage is 100%, so both parameters are already documented in the schema, including that email_id comes from send_email or list_emails and that llm_model is analytics-only. The description's 'by ID' restates rather than extends that, 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?

The description opens with a specific verb and resource ('Read a complete workspace email by ID') and clarifies that the full record, not a summary, is returned. It does not explicitly name how it differs from siblings such as get_email_raw or get_email_events, leaving that differentiation to the agent.

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 implied by 'by ID' and by naming the parameter source mentally, but there is no explicit statement of when to prefer this over get_email_raw, get_email_events, or list_emails. The error note ('unknown or inaccessible email returns an error') is the only conditional guidance offered.

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