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

zoho-bookkeeper-mcp

by bu5hm4nn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_invoice

Read-only

Retrieve detailed information about a specific invoice, including line items and customer details.

Instructions

Get detailed information about a specific invoice. Returns full invoice details including line items and customer info.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "get_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idNoZoho org ID (uses ZOHO_ORGANIZATION_ID env var if not provided)
invoice_idYesInvoice ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to reiterate safety. It adds value by specifying the return includes line items and customer info, but does not disclose other behavioral traits like pagination or performance.

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 concise sentences with no wasted words. First sentence clearly states action and target, second clarifies return content. Information is front-loaded.

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?

Without an output schema, the description adequately compensates by stating it returns full invoice details including line items and customer info. For a read-only tool with annotated safety, this is nearly complete. Could mention related tools or prerequisites, but is sufficient for its simplicity.

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%—both parameters are described in the schema. The description does not add any new meaning beyond what the schema provides, so baseline 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?

Description clearly uses verb 'Get' and specific resource 'invoice', stating it returns full invoice details with line items and customer info. This distinguishes it from sibling list_invoices which returns a list, and other get tools like get_invoice_attachment.

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 explicit guidance on when to use this tool versus alternatives such as list_invoices or get_invoice_attachment. The description implies it's for retrieving a single invoice's full details, but does not state when not to use it or mention other related tools.

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