moneylover-mcp

list_wallets

Read-only

Retrieve all Money Lover wallets with their currency and balance so you can resolve a user-mentioned wallet name into the exact spelling other tools expect.

Instructions

List every wallet in the Money Lover account with its currency and current balance. Use it to resolve a wallet name the user mentioned into the exact spelling the other tools expect. For totals or spending use summarize_spending; for categories use list_categories. Behavior: balances are served from a short-lived cache (from_cache says so); pass refresh only when the user explicitly needs a live figure, because recomputing is slow on large accounts. Archived wallets are included and flagged; they cannot receive new transactions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`refresh`	No	Set to true to bypass the short-lived cache and fetch live balances. Slow on large accounts, so leave it unset (default false) unless the user explicitly needs a live figure.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`wallets`	Yes
`from_cache`	Yes	True when served from the short-lived cache; balances may then be a few minutes old.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Oct 18, 2026

changedInput schema / properties / refresh / description

Previous value: -"Bypass the cache and fetch live balances (slow on large accounts)."New value: +"Set to true to bypass the short-lived cache and fetch live balances. Slow on large accounts,\nso leave it unset (default false) unless the user explicitly needs a live figure."

Changed4 schema fields changedv0.3.2Oct 18, 2026
- addedOutput schema / $defs / WalletOut / properties / archived / description
```
Added value: +"Archived wallets still appear in listings but reject new transactions."
```
- addedOutput schema / $defs / WalletOut / properties / currency / description
```
Added value: +"ISO currency code of the wallet, e.g. IDR."
```
- addedOutput schema / $defs / WalletOut / properties / excluded_from_total / description
```
Added value: +"Excluded by the user from Money Lover's own total balance."
```
- addedOutput schema / $defs / WalletOut / properties / name / description
```
Added value: +"Name to pass to other tools."
```
First observedv0.2.0Oct 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only provide readOnlyHint=true, but the description adds substantial behavior: cached balances, the from_cache indicator, performance cost of refresh on large accounts, and that archived wallets are included, flagged, and cannot receive new transactions. No contradiction with annotations.

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?

Front-loads the core purpose, then routes the agent to alternatives, then adds behavior. Five sentences, each earning its place with no filler or repetition.

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?

An output schema exists, so return values need not be explained. The description covers purpose, sibling routing, caching/refresh behavior, and archived-wallet caveats, which is complete for a read-only list tool.

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% and the sole refresh parameter is already fully documented in the schema. The description restates the cache-bypass guidance rather than adding new syntax, format, or edge-case detail beyond the schema. Baseline 3 applies.

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?

States the specific verb 'List' and resource 'wallet', plus the returned fields (currency, balance), and explicitly distinguishes itself from summarize_spending and list_categories. An agent can identify its role without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance ('resolve a wallet name the user mentioned into the exact spelling the other tools expect') and names alternatives for totals/spending and categories. Also states the condition for using the refresh parameter.

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

Deploy Server