Exports all historical API requests from local SQLite into a clean JSON file for auditing, backup, or analysis; optionally specify a target path.
Export all historical requests from local SQLite into a clean JSON file.
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | No | Target JSON file path (default: ~/.api-vault/api_vault_export_<timestamp>.json) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does disclose the source store (local SQLite) and the output artifact (JSON file), but says nothing about whether an existing file at file_path is overwritten, roughly how large an export can be, permissions needed, or what the call returns.
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?
One front-loaded sentence with zero filler; purpose, source, and output form arrive immediately. It is efficient, though the brevity trades away useful detail on the write-and-return behavior.
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?
For a one-parameter tool this covers the essentials, but with no output schema the description should say what comes back (e.g., written path or count) and whether existing files are replaced. Those gaps matter because the tool writes to disk.
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?
Schema coverage is 100% and the single optional file_path parameter already documents its meaning and default path. The description adds no further semantics such as path format constraints or overwrite behavior, so the schema does the heavy lifting.
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 and resource: export all historical requests into a JSON file, including the data source (local SQLite). It implicitly contrasts with search_history by emphasizing 'all' history rather than a filtered query, though it never names the sibling.
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?
No explicit when-to-use or when-not-to-use guidance. The word 'all' hints that this is the unfiltered bulk path versus search_history, but that inference is left entirely to the agent, and nothing is said about preconditions such as an existing history.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.