ExpenseTracker

Export Expenses

export_expenses

Export expense records within a specified date range, optionally filtered by category, as CSV text for direct pasting into spreadsheets.

Instructions

Export expenses in a date range as CSV text (can be pasted into a spreadsheet).

Input Schema

TableJSON Schema

Name	Required	Description
`category`	No	Optional — restrict to a single category.
`end_date`	Yes	End date (YYYY-MM-DD), inclusive.
`start_date`	Yes	Start date (YYYY-MM-DD).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

There are no annotations, so the description carries the full burden. It does disclose the output is CSV text and pasteable into a spreadsheet, which is useful behavioral context. However, it does not mention whether the export is read-only, whether headers are included, or how edge cases like empty results are handled.

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?

A single, front-loaded sentence that states the core action, scope, and output format. The spreadsheet note adds practical value without padding.

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

Completeness4/5

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

The tool is simple, has full schema coverage, and an output schema is present, so return values do not need to be detailed. The description covers the essential purpose and output format, though it could briefly mention the optional category filter.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description reinforces the date-range concept but adds no new meaning beyond the schema, and it does not mention the optional category filter.

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 action (export), the resource (expenses), the scope (date range), and the output format (CSV text). This differentiates it from sibling tools like list_expenses or search_expenses, which do not imply a spreadsheet-ready export format.

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?

The description implies the tool is for exporting data for spreadsheet use, but it does not explicitly state when to choose this over list_expenses, search_expenses, or summarize_expenses. No alternatives or exclusion criteria are mentioned.

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

Deploy Server