Skip to main content
Glama
Sign In
zoho-bookkeeper-mcp

zoho-bookkeeper-mcp

by bu5hm4nn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_vendor

Read-only

Retrieve detailed information about a specific vendor to confirm vendor IDs before creating expenses, bills, or vendor payments.

Instructions

Get detailed information about a specific vendor. Use this to confirm a vendor_id before creating expenses, bills, or vendor-payment categorizations.

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": {
      "vendor_id": "<vendor_id>"
    },
    "name": "get_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idNoZoho org ID (uses ZOHO_ORGANIZATION_ID env var if not provided)
vendor_idYesVendor ID (contact_id in Zoho Books)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that it returns 'detailed information' and its intended use, further clarifying behavior without contradiction.

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 purpose and usage guidance. Every sentence earns its place with no redundancy or fluff.

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 read-only retrieval tool with simple parameters, the description provides sufficient context. It lacks specifics about return fields or errors, but the usage guidance and schema compensate.

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 coverage is 100% (all parameters have descriptions). The description does not add new semantic information beyond the schema, so baseline of 3 is appropriate.

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: 'Get detailed information about a specific vendor.' It distinguishes from siblings like list_vendors (which lists) and get_contact (which is for contacts), and provides specific use cases.

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 explicitly says when to use the tool: 'Use this to confirm a vendor_id before creating expenses, bills, or vendor-payment categorizations.' This gives clear context for invocation.

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

Deploy Server

Other Tools