Hundo

propose_transaction

Propose a new income or expense transaction. Returns a proposal id; to record it, call the confirm_proposal tool with the returned proposalId after the user approves (there is no UI button or proposal card to click in this context). Validate account exists and is owned by the user before calling.

MCP note: this tool only CREATES a pending proposal; nothing is recorded until confirm_proposal is called.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	YYYY-MM-DD.
`type`	Yes
`amount`	Yes	Amount in MAJOR units (the displayed amount, e.g. 12.34 for $12.34, 50000 for Rp 50,000). The server scales to storage units; never pre-multiply by 100.
`currency`	Yes	3-letter currency code. May differ from the account's currency; the server records an exchange rate to convert into the account currency.
`accountId`	No	Id of the financial account. Omit only in the email-import pipeline when the source email is genuinely ambiguous about which account paid - the user will pick one via the proposal card's Edit button. In chat, always pass a real id (ask the user instead of guessing). Do not pass an empty string; omit the field entirely instead.
`categoryId`	No	Id of one of the user's categories, from their category list: the one that best matches what was bought or paid. Set it on every income and expense; omit it only when no category reasonably fits. Never a category name, and never an id that is not in the list.
`envelopeId`	No
`description`	Yes
`exchangeRate`	No	Rate to convert the amount into the account's currency, used only when currency differs from the account. Usually omit - the server auto-fetches the rate as of the date.
`editsProposalId`	No	Id of an existing pending proposal to update in place. Pass this when the user asks to modify a proposal you previously made (e.g. 'make it $50 instead'). Look up current ids with listPendingProposals if you're unsure. Omit when proposing something new.
`alreadyInBalance`	No	Set true only for a payment the account's balance already holds, which you know in one of two ways: you compared a list from the user's bank with the ledger (ACCOUNT VIEWS) and the line is dated on or before the account's addedOn (from getAccounts), or the user says the payment is already in the account's balance. Hundo then records it without moving the balance. Needs accountId, and an account that has an addedOn. Omit it for anything else, such as a payment the user tells you about to log: every other entry moves the balance.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

addedInput schema / properties / categoryId / description

Added value: +"Id of one of the user's categories, from their category list: the one that best matches what was bought or paid. Set it on every income and expense; omit it only when no category reasonably fits. Never a category name, and never an id that is not in the list."

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / alreadyInBalance

Added value: +{
+  "description": "Set true only for a payment the account's balance already holds, which you know in one of two ways: you compared a list from the user's bank with the ledger (ACCOUNT VIEWS) and the line is dated on or before the account's addedOn (from getAccounts), or the user says the payment is already in the account's balance. Hundo then records it without moving the balance. Needs accountId, and an account that has an addedOn. Omit it for anything else, such as a payment the user tells you about to log: every other entry moves the balance.",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / accountId / description

Previous value: -"Id of the financial account. Omit only in the email-import pipeline when the source email is genuinely ambiguous about which account paid — the user will pick one via the proposal card's Edit button. In chat, always pass a real id (ask the user instead of guessing). Do not pass an empty string; omit the field entirely instead."New value: +"Id of the financial account. Omit only in the email-import pipeline when the source email is genuinely ambiguous about which account paid - the user will pick one via the proposal card's Edit button. In chat, always pass a real id (ask the user instead of guessing). Do not pass an empty string; omit the field entirely instead."

changedInput schema / properties / exchangeRate / description

Previous value: -"Rate to convert the amount into the account's currency, used only when currency differs from the account. Usually omit — the server auto-fetches the rate as of the date."New value: +"Rate to convert the amount into the account's currency, used only when currency differs from the account. Usually omit - the server auto-fetches the rate as of the date."

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare this is not readOnly and not idempotent, which the description reinforces with 'nothing is recorded until confirm_proposal is called' — valuable extra context. It discloses the two-phase lifecycle and the validation requirement, going beyond the annotations. It does not cover error behavior for invalid account/category ids.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the return value, then the follow-up step, then the prerequisite. The MCP note is somewhat redundant with the first sentence, which costs a point, but the overall structure is efficient and non-repetitive.

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?

For an 11-parameter mutation tool with no output schema, the description covers the lifecycle, the follow-up call, and the account validation. It could say more about the pending-proposal state or the editsProposalId path, but the essentials for correct invocation are present.

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 coverage is 73%, so most parameters are documented in the schema. The description names type, amount, currency, date and description as the core inputs, but adds no format or constraint detail beyond what the schema already says. Baseline 3 is appropriate.

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 a specific verb and resource ('Propose a new income or expense transaction') and immediately distinguishes itself from the confirm step. The MCP note reinforces the two-phase nature, making it clearly separable from confirm_proposal and the edit variant.

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?

Explicitly names the alternative (confirm_proposal) with the returned proposalId and the condition (after user approval). Also states the account-validation prerequisite and clarifies that there is no UI button in this context, which is precisely the when/when-not guidance an agent needs.

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

All Hundo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?