Skip to main content
Glama
Sign In
Zoho CRM + Books MCP Server

Zoho CRM + Books MCP Server

by Mgabr90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

books_get_purchase_order

Retrieves a specific purchase order from Zoho Books by ID, returning its complete details and current status.

Instructions

Get a specific purchase order from Books by ID

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": {
      "purchase_order_id": "<purchase_order_id>"
    },
    "name": "books_get_purchase_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
purchase_order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It conveys that this is a read operation ('Get'), but does not mention edge cases (e.g., not found), permissions, or return format. Adequate but minimal.

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?

A single concise sentence that is front-loaded with the action and resource. Zero wasted words, perfect for an agent to quickly grasp.

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 tool's simplicity (one parameter, no output schema), the description is sufficient to invoke correctly. It could optionally mention the return value (the purchase order details), but that is implied by 'Get'.

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?

The description references 'by ID' which maps to purchase_order_id, but this adds minimal value beyond the schema's property name and type. The parameter is self-evident from the context, but no extra format or semantics are provided.

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 explicitly states the action (Get), the resource (a specific purchase order), and the scope (by ID). This clearly distinguishes it from siblings like books_get_purchase_orders (which lists all purchase orders), making the tool's purpose unambiguous.

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 implies the tool is for retrieving a single purchase order when the ID is known. It does not explicitly name alternatives or exclusions, but the 'by ID' phrasing clearly contrasts with list-style tools. Highly functional but slightly implicit.

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