Skip to main content
Glama
Mgabr90

Zoho CRM + Books MCP Server

by Mgabr90

books_create_payment

Create a payment in Zoho Books and allocate it to specific invoices. Input customer, payment method, total amount, and invoice allocations to settle balances.

Instructions

Create a payment in Books to apply against specific invoices. First use books_get_invoices to find invoice IDs and amounts, then create payment to apply against those invoices.

Example workflow:

  1. books_get_invoices({customer_id: "123"}) // Find unpaid invoices

  2. books_create_payment({customer_id: "123", amount: 1000, invoices: [{invoice_id: "inv-456", amount_applied: 1000}]})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesPayment date in YYYY-MM-DD format (e.g., "2024-12-31")
amountYesTotal payment amount (must equal sum of amount_applied across invoices)
invoicesYesList of invoices to apply payment against (get invoice details from books_get_invoices first)
customer_idYesCustomer ID (get from books_get_customers)
descriptionNoPayment description or notes
bank_chargesNoBank processing fees or charges
payment_modeYesPayment method (e.g., "cash", "check", "bank_transfer", "credit_card")
currency_codeNoCurrency code (e.g., "USD", "EUR")
exchange_rateNoExchange rate if different from base currency
reference_numberNoReference number (check number, transaction ID, etc.)
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. However, it only states the basic action and workflow. It does not mention side effects (e.g., invoices being marked paid), validation rules (such as amount equaling the sum of amount_applied), non-idempotency, or potential irreversible consequences. This is a significant gap for a financial mutation tool.

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 concise and front-loaded: the first sentence states the purpose, followed by a helpful example workflow. Every sentence earns its place, and it is appropriately sized for the tool's complexity.

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 the 10 parameters and no output schema, the description provides a clear usage pattern with the workflow example. However, it does not explain what happens on success (e.g., return value or confirmation) or describe failure conditions. Still, it is sufficiently complete for correct invocation when combined with the rich schema descriptions.

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 description coverage is 100%, so the baseline is 3. The description adds value through an example showing how to use customer_id, amount, and invoices, reinforcing relationships like the sum constraint. However, it does not provide additional semantics beyond what the schema already specifies.

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 function: 'Create a payment in Books to apply against specific invoices.' It uses a specific verb and resource, and the workflow example further clarifies its purpose. It is distinct from sibling tools like books_get_payments or books_record_bill_payment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to first use books_get_invoices to find invoice IDs and amounts, and provides a concrete example workflow. It does not explicitly mention when not to use this tool (e.g., for bill payments), but the focus on invoices and the example differentiate it from alternatives like books_record_bill_payment.

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/Mgabr90/zoho-mcp-server'

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