Server has 14 well-named tools with consistent verb_noun patterns (drebedengi_get_*, drebedengi_list_*, drebedengi_add_*, drebedengi_delete_*). All tools have descriptions (10-300 chars, within baseline). However, input schemas are inferred from Python function signatures rather than explicitly visible in JSON Schema format. Parameter descriptions exist in docstrings but are not formally attached to schema definitions. Output schemas are completely undocumented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance or categorization. Security: credentials injected via environment (good), but no permission gates on destructive tools (delete_transaction). Composition is sound: tools are single-purpose and chainable (e.g., list_places → add_expense). Read-only tools dominate (10/14), reducing risk.
Record an expense transaction. sum is in major currency units (tenge, rubles) — e.g. 500.0 for 500 tenge. The server converts to minor units (tiyn, kopecks) before sending to the API.
Record an income transaction. sum is in major currency units (tenge, rubles) — e.g. 1500.0 for 1500 tenge.
Record a transfer between accounts. Creates two linked transactions (from and to).
Delete a transaction by ID. For transfers, deletes both legs (from and to records).
Return current account balances grouped by place and currency. Each record contains: sum (integer string in minor currency units — kopecks/tiyn/cents, divide by 100 to get the major unit amount), currency_id, place_id, place_name, currency_name, currency_default, is_for_duty, is_credit_card, parent_id, sort.
Output schemas completely undocumented. LLMs cannot predict response structure (e.g., drebedengi_get_balance returns dict with 'sum', 'currency_id', 'place_id', etc., but this is only in the description text, not in a formal schema). Agents cannot plan downstream tool calls or extract fields reliably.
Input schemas inferred from Python function signatures, not explicitly visible as JSON Schema. Parameter types and descriptions are in docstrings, not attached to schema definitions. FastMCP may auto-generate schemas, but this is not verifiable from the source code provided.
No error handling or recovery guidance. Destructive tool (drebedengi_delete_transaction) has no confirmation step, dry-run, or permission gate. Agents can delete transactions without safeguards.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Return a list of data changes that occurred after the given revision. Use this to incrementally sync data. Each record contains: revision, action_id (1=create, 2=update, 3=delete), object_type_id, object_id, date.
Return the current Drebedengi server revision number. Use this to detect data changes since a known revision.
Verify Drebedengi API credentials and connectivity. Returns status, current revision, and WSDL URL.
Return expense/income category tree. Each record contains: id, parent_id, name, type (2=income, 3=expense), is_hidden, sort, budget_family_id.
Return currency definitions. Each record contains: id, name, code, course (rate to default), ratio, is_default, is_autoupdate, is_hidden, is_investing, family_id.
Return account/place definitions (wallets, bank accounts, etc.). Each record contains: id, name, type, parent_id, is_hidden, is_for_duty, is_credit_card, icon_id, sort.
Return income source definitions. Each record contains: id, parent_id, name, type, is_hidden, sort, budget_family_id.
Return tag definitions. Each record contains: id, name, parent_id, is_hidden, is_family, sort.
Return transaction records (expenses, incomes, transfers). Each record contains: id, operation_type (1=income, 2=transfer, 3=expense), operation_date, sum (integer string in minor currency units — kopecks/tiyn/cents, negative for expenses and transfers out; divide by 100 for major unit amount), currency_id, place_id, budget_object_id (category/source id), comment, is_duty, group_id. Two modes: - By IDs: pass ids=[...] to fetch specific records. No other params needed. - By period: use period_from+period_to or r_period to fetch by date range. is_report=False (default) returns individual records; is_report=True returns aggregates.
drebedengi_list_transactions has 13 parameters with complex interdependencies (ids vs period_from+period_to vs r_period; is_report changes meaning of r_how). Dependencies are documented in the description but not enforced. LLMs may pass invalid combinations.
No pagination support visible. drebedengi_list_* tools may return unbounded results. If a user has 1000 categories or transactions, the response could exhaust context window. No limit, offset, or cursor parameters documented.