Valid accounts, providers, tickers, asset classes and categories. Read this before writing: trades and adjustments must use these values unless allow_new_values is set.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of explaining behavior. It does not explicitly state that the tool is read-only or safe, but the content (reference data) and guidance ('read before writing') strongly imply a non-destructive, informational purpose. A more explicit disclosure would improve this score.
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?
Two short, actionable sentences with no wasted words. The first sentence lists the data types, the second provides critical usage guidance. Optimal conciseness for the content.
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?
The tool has no parameters and no output schema, so the description needs only to explain what it returns and when to use it. It does both adequately. However, it could mention if the output is paginated or if there is a default format, but given the simplicity, this is sufficient.
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?
There are no parameters, so the schema coverage is trivially 100%. The description adds value by explaining the purpose of the returned data (valid values for writing operations), which goes beyond the empty schema.
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?
The description clearly states the tool returns valid accounts, providers, tickers, asset classes, and categories. It distinguishes itself from sibling writing tools (log_trade, record_balance_adjustment) by explicitly positioning it as a prerequisite reference read.
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?
The description explicitly advises 'Read this before writing' and notes that trades and adjustments must use these values unless allow_new_values is set. This provides clear context on when to use the tool, though it does not name an alternative tool for the 'allow_new_values' case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct domain operation: dashboard views, history, pricing, projections, reference data, tax reports, connections, transactions, trade logging, balance adjustments, and syncing. There is no overlap between read-only queries and mutation commands, so an agent should be able to select the right tool for a specific task without confusion.
All tools follow a consistent verb_noun pattern: get_dashboard, get_net_worth_history, get_prices, get_projection_config, get_reference_data, get_tax_report, list_connections, list_transactions, log_trade, record_balance_adjustment, refresh_prices, sync_connections. The verbs (get, list, log, record, refresh, sync) are clear and align with the noun they operate on.
Twelve tools is well-scoped for a personal finance/ledger server. Each tool covers a necessary aspect of the domain (viewing, reporting, data entry, sync), and none feel redundant or excessive. This fits the typical range for a coherent service.
The surface covers core read operations (dashboard, history, prices, reference data, tax, transactions), mutation operations (log_trade, record_balance_adjustment), and maintenance operations (refresh_prices, sync_connections). Missing could be an update/delete for transactions or connections, but the provided tools cover the primary lifecycle of a financial ledger without dead ends.
