Retrieve statistics for the local SQLite database, including file path, file size, and row counts for all tables, to check storage usage and verify data volume.
Get statistics about the local SQLite database, including database file path, file size, and row counts of all tables.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral load; 'Get statistics' makes the read-only, side-effect-free nature evident, and it discloses the shape of the returned information without any output schema. It stops short of stating what the file size units are or whether counts include internal tables.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with the action first and the returned fields trailing. Every clause earns its place; nothing to trim.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description adequately covers what the agent gets back (path, size, row counts) and that it is a read. Minor gaps remain around units and exact return structure, but an agent can call this correctly without more.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumerated return contents go beyond parameter concerns without adding noise.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get statistics') and resource ('local SQLite database'), and enumerates what is reported: file path, file size, table row counts. This is clearly distinguishable from the only related sibling, db_reset, though it does not explicitly name that distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the self-explanatory name and the 'statistics' framing, but the description never says when to call this versus alternatives or what conditions make it useful (e.g., diagnostics before db_reset). No exclusions offered.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.