Skip to main content
Glama

Hail Communication for AI

Get an email attachment

get_email_attachment
Read-onlyIdempotent

Return a temporary download URL for an inbound email attachment.

    The URL expires after approximately five minutes and requires no authorization header.
    Returns ``url``, or an error for an unavailable attachment.

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>",
      "attachment_id": "<attachment_id>"
    },
    "name": "get_email_attachment"
  }
}

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.
attachment_idYesAttachment ID, from the ``attachments`` of ``get_email``.

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

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses behavior an agent cannot get elsewhere: the URL expires after roughly five minutes and requires no authorization header. It also states the failure mode ('an error for an unavailable attachment'), which is exactly the kind of operational context the annotations do not convey.

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, front-loaded with the purpose, followed by the expiry/auth behavior. No repetition of the title and no filler; every clause carries information an agent needs.

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 simple two-required-parameter read tool with an output schema and full annotation coverage, the description supplies the missing operational facts (expiry, no auth, error case). The only shortfall is the absence of sibling routing guidance, which matters slightly given get_email_raw and get_email exist in the same family.

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%, and the schema already documents both required parameters with their provenance (list_emails for email_id, get_email for attachment_id). The description adds nothing about parameters, so the baseline of 3 applies; llm_model is only explained in the schema itself.

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?

The description opens with a specific verb and resource: 'Return a temporary download URL for an inbound email attachment.' The scope qualifier 'inbound' and 'attachment' clearly distinguishes it from siblings like get_email_raw or get_email, so an agent can select it without inspecting 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 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: an agent infers it should call this when it needs to fetch attachment content rather than raw email or event data. There is no explicit 'use this instead of X' routing, nor any statement of when-not to call it (e.g., outbound attachments, already-downloaded content).

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