Zoho CRM + Books MCP Server

books_get_payments

Retrieve all payments from Zoho Books with filtering, sorting, and pagination options.

Instructions

Get all payments from Books

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "books_get_payments"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`per_page`	No
`filter_by`	No
`sort_order`	No
`customer_id`	No
`search_text`	No
`sort_column`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The schema includes readOnlyHint: true and idempotentHint: true, which already indicate a safe read operation. The description adds no behavioral context beyond what the annotations provide, such as pagination behavior, result size, or rate limits. It does not contradict the annotations, but it also adds no value.

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

Conciseness3/5

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

The description is a single concise sentence with no fluff, which is a positive. However, it is under-specified, functioning more like the tool name itself than a helpful explanation. It lacks any structural elements to guide understanding of the tool's inputs or behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 7 parameters, no output schema, and no annotations beyond hints, the description should provide substantial context about pagination, filtering, and result format. It does none of this, leaving a significant gap for agents trying to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any of the 7 parameters (e.g., page, per_page, filter_by, sort_order). With such low coverage, the description should compensate, but it offers zero parameter meaning, leaving agents to infer from parameter names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all payments from Books' clearly identifies the action (get all) and the resource (payments in Books). It is specific enough to distinguish from related tools like books_get_invoices or books_get_bill_payments, though it does not explicitly differentiate itself from siblings.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as books_get_bill_payments or books_get_invoices. The description does not mention pagination, filtering, or typical use cases, leaving the agent without context for selection.

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

Deploy Server