Skip to main content
Glama
Operamatix

zoho-books-mcp

by Operamatix

zoho_categorize_bank_txn

Categorizes uncategorized bank-feed lines in place, clearing the queue without creating duplicate transactions. Automatically derives amount, date, and maps the offset account for deposits, expenses, or payments.

Instructions

Categorize an uncategorized bank-feed line IN PLACE (clears the feed queue without creating a parallel transaction). Route: POST /banktransactions/uncategorized/{transaction_id}/categorize (generic types) or .../categorize/{categorize_as} (expenses|customerpayments|vendorpayments). CONVENIENCE: pass offset_account_id (the non-bank side) and the wrapper maps it to the right field — for a money-IN deposit type it becomes from_account_id (credited) with to_account_id = the bank (debited); for categorize_as=expenses it becomes account_id with paid_through_account_id = the bank. amount/date and the bank account are AUTO-DERIVED from the feed line when omitted (pass bank_account_id to make that list lookup reliable). VERIFIED: owner contribution -> transaction_type='deposit', offset_account_id=; bank fee -> categorize_as='expenses', offset_account_id=. NOTE: offset auto-mapping assumes money-IN; for money-OUT/other directions pass explicit from_account_id/to_account_id/account_id or a full body. Gated by ZOHO_ALLOW_WRITES; Zoho's response is returned verbatim on error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoAdditional payload fields, merged last (highest precedence).
dateNoYYYY-MM-DD. Optional — auto-derived from the feed line if omitted.
amountNoOptional — auto-derived from the feed line if omitted.
account_idNoExplicit override.
categorize_asNoModule-specific sub-endpoint.
to_account_idNoExplicit override (the bank for deposits).
transaction_idYesThe uncategorized feed line id.
bank_account_idNoThe feed line's bank account. Optional — auto-derived from the line if omitted; passing it makes amount/date lookup reliable.
from_account_idNoExplicit override (offset/source for deposits).
transaction_typeNoGeneric type, e.g. deposit, owner_contribution, interest_income, other_income.
offset_account_idNoThe non-bank account (equity for a contribution, expense account for an expense). Auto-mapped to the correct field.
paid_through_account_idNoExplicit override (the bank for expenses).
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: auto-derivation of amount/date, offset auto-mapping assumptions, the effect on the feed queue, and error handling (verbatim Zoho response). No contradictions exist.

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?

The description is somewhat lengthy but well-structured with clear labels (CONVENIENCE:, VERIFIED:, NOTE:). It is front-loaded with the core purpose. A slight reduction in detail could improve conciseness, but every sentence adds useful information.

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?

Given 12 parameters, no output schema, and nested objects, the description covers essential usage patterns, auto-derivation behavior, and error handling. It could be more complete by describing the success response format, but the provided context is sufficient for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds significant value beyond the schema by explaining inter-parameter relationships (offset auto-mapping, auto-derivation reliance on bank_account_id) and providing concrete examples. This elevates the score to 4.

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?

The description clearly states the tool categorizes an uncategorized bank-feed line in place, using a specific verb and resource. It distinguishes from sibling tools by describing the unique operation (clearing the feed queue without creating a parallel transaction) and provides routing details.

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?

The description gives explicit guidance on when to use convenience features (passing offset_account_id) and when to avoid them (money-OUT directions). It provides verified examples for common cases (owner contribution, bank fee) and notes the gating by ZOHO_ALLOW_WRITES.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Operamatix/zoho-books-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server