zoho-bookkeeper-mcp

categorize_bank_transaction_generic

Categorize uncategorized bank transactions into generic types such as deposits, transfers, and owner contributions. Ideal for bank-native bookkeeping flows not covered by expense or invoice matching.

Instructions

Categorize an uncategorized bank transaction into a general Zoho bank transaction. Use this for deposits, transfers, owner contributions/drawings, interest income, other income, sales without invoices, expense refunds, sales returns, and similar bank-native bookkeeping flows. Prefer matching or expense/vendor/customer payment categorization when those are a better fit than a generic bank transaction.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transaction_id": "<transaction_id>",
      "transaction_type": "<transaction_type>",
      "from_account_id": "<from_account_id>",
      "to_account_id": "<to_account_id>",
      "amount": "<amount>",
      "date": "<date>"
    },
    "name": "categorize_bank_transaction_generic"
  }
}

Input Schema

Name	Required	Description
`organization_id`	No	Zoho org ID (uses ZOHO_ORGANIZATION_ID env var if not provided)
`transaction_id`	Yes	Uncategorized bank transaction ID
`transaction_type`	Yes	Generic bank transaction type to create
`from_account_id`	Yes	Source account ID for the transaction
`to_account_id`	Yes	Destination account ID for the transaction
`amount`	Yes	Transaction amount
`date`	Yes	Transaction date (YYYY-MM-DD)
`payment_mode`	No	Optional payment mode such as Cash or Cheque
`exchange_rate`	No	Optional exchange rate
`reference_number`	No	Optional reference number
`description`	No	Optional description or memo
`customer_id`	No	Optional customer ID
`currency_id`	No	Optional currency ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false (mutation) and openWorldHint=true. The description doesn't contradict these, but it adds little beyond saying 'Categorize.' It doesn't describe side effects (e.g., whether the original transaction status changes, if new records are created, or any constraints). The behavioral transparency is adequate but not enriched beyond the 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?

The description is two sentences long, front-loaded with the primary action, and every sentence adds value. There is no redundancy or unnecessary detail.

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 a tool with 13 parameters (6 required) and no output schema, the description covers the main context: what the tool does, when to use it, and how it differs from siblings. It could mention expected return values or success indicators, but the overall completeness is high given the simplicity of the task and the rich schema.

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?

The input schema has 100% description coverage for all 13 parameters, so the schema itself documents the parameters well. The tool description does not add further meaning to the parameters; it only lists use cases. Baseline 3 is appropriate given full schema coverage.

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's purpose: 'Categorize an uncategorized bank transaction into a general Zoho bank transaction.' It lists specific transaction types (deposits, transfers, etc.) and distinguishes itself from sibling tools like categorize_bank_transaction_as_customer_payment by using 'generic' and advising when to prefer alternatives.

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 provides explicit guidance on when to use this tool: 'Use this for deposits, transfers, owner contributions/drawings, interest income, other income, sales without invoices, expense refunds, sales returns, and similar bank-native bookkeeping flows.' It also tells when not to use it: 'Prefer matching or expense/vendor/customer payment categorization when those are a better fit.'

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

Deploy Server