Skip to main content
Glama
Sign In
Timbre

Timbre

by alejandrosml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

export_mail

Save a message or its entire conversation as a PDF, original .eml, or plain text in Timbre's attachments folder for reading, printing, archiving, or sharing without overwriting files.

Instructions

Keep a message or its whole conversation as a file in the user's Timbre attachments folder: a PDF to read or print (default), the original .eml (Mail opens it) to archive or pass on, or plain text. Never overwrites a file.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe message; with thread, any message of the conversation.
formatNo"pdf" (default), "eml" (the original message: Mail opens it; one file per message) or "txt".
threadNoThe whole conversation it belongs to (up to 200 messages).

Output Schema

NameRequiredDescriptionDefault
noteYes
filesYesThe files made, in Timbre's attachments folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false), the description discloses where the side effect lands (the user's Timbre attachments folder) and adds the important guarantee 'Never overwrites a file', which is real behavioral context an agent cannot get from the annotation flags alone. It omits file-naming behavior, collisions, and any size or auth constraints.

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?

A single dense sentence that front-loads the action and destination, then the format choices, then the non-overwrite guarantee. Every clause carries information; nothing is padding.

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?

With an output schema present, full parameter coverage, and annotations covering the safety profile, the description supplies what remains: destination folder, format intent, and non-destructive write behavior. Only minor gaps (file naming, where the resulting path appears) keep it from 5.

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 the baseline is 3. The description restates the format options and their intent but adds little beyond the schema's own descriptions (it even omits the 200-message thread cap that the schema documents), so it does not meaningfully deepen parameter meaning.

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 gives a specific verb and resource: keep a message or its whole conversation as a file in the Timbre attachments folder, and it enumerates the three output formats. It does not explicitly name the neighboring tools it might be confused with (save_attachment, open_in_mail), so it falls short of a full 5.

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 context is given only at the format level ('a PDF to read or print', '.eml to archive or pass on'), which is implied guidance about which option to pick. There is no explicit statement of when to use this tool instead of save_attachment or open_in_mail, which is the main alternative an agent would weigh.

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