zoho-bookkeeper-mcp

list_vendors

Read-only

Retrieve vendor contacts to obtain vendor IDs needed for categorizing expenses, bills, and bank payments.

Instructions

List vendor contacts only. Use this to find vendor_id values for expenses, bills, and vendor-payment bank categorization workflows.

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": "list_vendors"
  }
}

Input Schema

Name	Required	Description
`organization_id`	No	Zoho org ID (uses ZOHO_ORGANIZATION_ID env var if not provided)
`status`	No	Filter by status
`search_text`	No	Search by vendor name or company
`sort_column`	No
`page`	No
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already provide readOnlyHint and openWorldHint, indicating safe read behavior. The description adds minimal behavioral detail beyond that (e.g., no mention of pagination or data freshness). No contradictions.

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?

Two sentences, front-loaded with the core action and purpose. Every word is necessary, no fluff.

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

Completeness3/5

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

Tool has 6 parameters and no output schema. Description does not explain return fields or pagination behavior, leaving gaps for a full understanding. Adequate but incomplete.

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

Parameters2/5

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

Schema description coverage is 50%, but the description adds no meaning to parameters (e.g., does not explain filters or sorting). Baseline 3 is not justified because the description fails to compensate for the missing schema descriptions.

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 verb 'List' and resource 'vendor contacts only'. It explicitly mentions the use case: finding vendor_id values for expenses, bills, and vendor-payment bank categorization workflows, distinguishing it from sibling tools like list_contacts or list_bills.

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 provides a clear context for use: to find vendor_id values for specific workflows. It does not explicitly state when not to use or mention alternatives, but the purpose is specific enough to guide the agent.

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

Deploy Server