Skip to main content
Glama
hail-hq

hail

Official
by hail-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get raw email

get_email_raw
Read-onlyIdempotent

Get a fetchable URL for an email's original MIME source.

Instructions

Get a fetchable URL for an email's original MIME source.

    Returns ``{"url": "<presigned-s3-url>"}`` — a short-lived
    (~5 minute) link to the full raw RFC822 message. Fetch the URL
    directly to read the complete original; it needs no auth header.
    Raw source exists for **inbound** mail only — outbound ids return
    ``{"error": "resource not found"}``.

Input Schema

NameRequiredDescriptionDefault
email_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.29.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: presigned S3 URL, ~5 minute lifetime, no auth header needed to fetch, inbound-only availability, and the exact error payload for outbound ids. These are exactly the operational facts an agent needs before calling.

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?

Front-loads the core action in one sentence, then layers expiration, auth-free fetching, and the inbound-only caveat. No filler; every line carries an actionable fact.

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?

An output schema exists, yet the description still spells out the return shape and the failure case, closing the loop on the single-parameter, single-purpose surface. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and email_id is undocumented in the schema, so the description must compensate. It adds the key semantic constraint — the id must refer to inbound mail or an error is returned — though it doesn't say where to obtain a valid email_id (e.g., from list_emails).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returning a fetchable URL for an email's original MIME source. This clearly separates it from siblings like get_email (metadata) and get_email_attachment, so an agent knows exactly what this returns without opening the schema.

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?

Explicitly scopes usage to **inbound** mail and warns that outbound ids fail with "resource not found", which is a genuine when-not condition. It never names an alternative sibling (e.g., get_email for parsed content), so routing guidance is strong but not complete.

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