Skip to main content
Glama
hgn

Notmuch

by hgn

Thread overview

mail_thread_overview
Read-only

Get a one-line-per-message overview of an email thread with date, size, sender, and subject changes. Use it to decide which messages to read in full before fetching the entire thread.

Instructions

One line per message: index, date, size, from, and a marker when the subject changes from the thread's root subject.

Use this before mail_read_thread on any thread you have not looked at yet, especially a long one: it costs a fraction of the tokens and lets you decide which one or two messages to actually read in full, instead of pulling all eighty. Do not use it in place of mail_read_thread when you already know you need the full content.

Args: thread_id: A thread identifier as returned by mail_search (with or without the 'thread:' prefix). layout: 'tree' (the actual reply nesting, from notmuch's own thread structure; for a patch series with parallel discussion strands this is materially different from linear order) or 'flat' (linear oldest-first order, matching mail_read_thread's [N/M] numbering).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layoutNotree
thread_idYes
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description adds context on token efficiency, output fields, and the layout parameter's impact on the structure. It fully discloses behavioral traits beyond annotations.

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?

The description is efficiently written with no wasted words. It front-loads the output format, then gives usage guidance, then parameter details. Every sentence adds value.

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?

Given no output schema, the description fully explains what the output contains. It covers all aspects: what the tool does, when to use it, parameter details, and behavioral traits. For a tool with only 2 parameters and straightforward output, this is complete.

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

Parameters5/5

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

Schema coverage is 0%, but the description provides detailed semantics: thread_id is explained as a thread identifier from mail_search (with optional prefix), and layout is explained in depth, including the difference between 'tree' and 'flat' and the relevance to patch series. This fully compensates for the lack of schema documentation.

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 clearly states the output format (one line per message with index, date, size, from, subject change marker) and explicitly contrasts with mail_read_thread. It leaves no ambiguity about what the tool does.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (before mail_read_thread on unseen or long threads) and when not to (when full content is needed). It also provides a clear rationale (token cost) and a concrete alternative (mail_read_thread).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hgn/mcp-server-notmuch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server