Loading ToolBench
MCP server for Realbyte Money Manager API - lets AI assistants manage personal finances through the Realbyte Money Manager Android app (PC Manager web server)
18 tools with complete schemas and descriptions, but quality is uneven. Most tools have adequate naming (verb_noun pattern) and parameter descriptions, but many descriptions are generic or lack actionable context. Output schemas are not documented. Error handling is present but minimal. No tool annotations (readOnlyHint/destructiveHint). Parameter constraints are sometimes missing (e.g., transaction_create's mbCash lacks min/max bounds). Some tools have overly verbose descriptions that could be tightened. Composition is reasonable, tools are single-purpose, but chaining IDs are not always returned (e.g., transaction_list doesn't return mbid for follow-up calls).
Creates a new asset
Deletes an asset
Retrieves all assets in a hierarchical structure
Updates an existing asset
Creates a new credit card
Retrieves all credit cards in a hierarchical structure
Updates an existing credit card
Output schemas not documented. Tools return data but LLMs cannot plan downstream calls without knowing response structure. E.g., transaction_list, asset_list, dashboard_get_overview lack documented return types.
Numeric parameters lack bounds. mbCash in transaction_create/update, assetMoney in asset_create/update, notPayMoney in card_create/update have no min/max constraints. LLMs can pass absurd values (negative, zero, or extremely large).
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without parsing descriptions. transaction_delete, asset_delete should be marked destructive.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | <=2025-11-25 | v2 |
Retrieves monthly asset chart data for a specific asset
Retrieves dashboard overview with asset summary, monthly trends, and asset/debt ratios
Retrieves initial application data: categories, payment types, assets, books
Exports transactions to Excel. The Money Manager API returns an HTML file with Excel metadata, not a proper XLSX binary. This format works with .xls; if .xlsx is requested it is auto-corrected to .xls with a warning in the response message.
Retrieves financial summary statistics for a date range
Creates a new income or expense transaction
Deletes one or more transactions
Lists transactions within a date range (handles three XML empty-edge cases)
Updates an existing transaction
Creates a new transfer between assets
Updates an existing transfer. Note: does NOT update in place - the server creates a NEW transfer with a NEW id and invalidates the old one. Find the new id via transaction_list filtered by the source asset and date (look for the inOutCode '3' Transfer-Out row).
Chaining IDs missing from responses. transaction_list does not return mbid; asset_create/update do not document returned assetId. Agents cannot chain calls without extra lookups.
Generic descriptions on discovery tools. asset_list, card_list, dashboard_get_overview say 'Retrieves...' but do not explain when to call them or what structure they reveal. LLMs cannot distinguish between similar tools.