mailpouch

Overview Schema Source Related Servers Discussions Admin

FTS Index Status

fts_status

Read-only

Get the local FTS5 index's file path, row count, and on-disk size. Returns unavailability status if the required SQLite module is not installed.

Instructions

Report the path, row count, and on-disk size of the local FTS5 index. Returns { available: false } when better-sqlite3 is not installed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account_id`	No	Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`dbPath`	No
`reason`	No
`available`	Yes
`messageCount`	No
`databaseBytes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.1.0Jul 5, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}

First observedv3.0.77Jun 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=true. The description adds the important behavioral detail that the tool returns { available: false } when better-sqlite3 is not installed, which is beyond what annotations provide.

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 consists of two concise, front-loaded sentences with no wasted words. Every sentence adds value: the first states output, the second handles an edge case.

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?

For a simple read-only status tool, the description is complete. It specifies exactly what is reported, handles the missing dependency case, and the output schema (exists) can detail the return format. No gaps.

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?

The input schema covers the single optional parameter (account_id) with a full description. The description adds no additional parameter information, so it meets the baseline for high schema coverage.

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 tool reports path, row count, and on-disk size of the local FTS5 index. The verb 'Report' and specific resource 'FTS5 index' distinguish it from sibling tools like fts_rebuild or fts_search.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. Sibling tools exist (e.g., fts_rebuild, fts_search) but no context is given for when to prefer fts_status.

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

Deploy Server