Skip to main content
Glama

Mail Index Rebuild

mail_index_rebuild

Rebuild the FTS5 mail search index from disk to refresh stale data and restore accurate Apple Mail search results.

Instructions

(Re)build the FTS5 index from disk. Run again when the index is stale.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mail_index_rebuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never says whether the existing index is dropped and rebuilt (a destructive, potentially long operation), whether the rebuild can be run concurrently with searches, or what happens on failure. The only behavioral hint is 'from disk', which implies the source data but not the cost or safety profile.

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?

Two short sentences, front-loaded with the action and followed by the maintenance trigger; no filler. The terseness borders on under-specification given the unexplained 'FTS5' jargon, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a state-mutating maintenance operation with zero annotations and an undocumented parameter, the description leaves out cost, scope, and safety. An agent cannot decide whether to run this safely without guessing.

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

Parameters2/5

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

The single 'mailbox' parameter has 0% schema description coverage and the description never mentions it, so the crucial question of whether the rebuild covers one mailbox or the whole account (the null default) is left unanswered. The description adds no meaning beyond the schema here.

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?

Names a specific verb and resource: '(Re)build the FTS5 index from disk.' An agent can tell this is an index-maintenance operation rather than a mail read/write, and no sibling competes for the same job. It stops short of explicitly differentiating itself, but the resource is distinctive enough.

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?

Gives one concrete trigger: 'Run again when the index is stale.' It does not say how to tell the index is stale, whether this is required after setup, or what to do instead (e.g. search directly), so the when-to-use guidance is only partial.

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