Skip to main content
Glama

Hail Communication for AI

Get raw email

get_email_raw
Read-onlyIdempotent

Return a temporary download URL for an inbound email's original MIME source.

    The URL expires after approximately five minutes and requires no authorization header.
    Raw source is available only for inbound emails.
    Returns ``url``, or an error for an unavailable 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": "get_email_raw"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesInbound email ID, from ``list_emails`` with direction ``inbound``.
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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, but the description adds genuinely new behavior: the URL expires after about five minutes and needs no authorization header. It also discloses the failure mode (error for an unavailable email). Rate limits and whether the URL is single-use are not mentioned.

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?

Three short lines, with the core action and the returned artifact front-loaded, then expiring/auth constraints, then error behavior. Every sentence carries information; the return-value note slightly overlaps with the existing output schema.

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 two-parameter read tool with full schema coverage, annotations, and an output schema, this covers purpose, availability constraint, URL lifetime, auth requirement, and error behavior. Nothing an agent needs to call it correctly appears to be missing.

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%, so email_id and llm_model are already documented; the baseline is 3. The description reinforces the inbound-only constraint on email_id but adds no format or syntax detail beyond the schema, and says nothing about the optional llm_model 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?

States a specific verb and resource: 'Return a temporary download URL for an inbound email's original MIME source.' This clearly separates it from sibling get_email, which returns parsed content. It stops short of naming that sibling, so the differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete applicability rule — raw source exists only for inbound emails — and the input schema points to list_emails with direction 'inbound' for the ID. No explicit 'use get_email instead for parsed content' routing statement, so it falls short of the 5 bar.

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