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

Zoho CRM + Books MCP Server

by Mgabr90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

books_submit_purchase_order_for_approval

Submit a purchase order for approval in Zoho Books to initiate the approval workflow and secure authorization.

Instructions

Submit a purchase order for approval

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_submit_purchase_order_for_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
purchase_order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full transparency burden. It only states 'submit for approval' without disclosing side effects (e.g., status changes), permissions, or error conditions. The mutating nature is implied but not elaborated.

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

Conciseness4/5

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

The description is a single, front-loaded sentence with no unnecessary words. It is concise, though the brevity reflects under-specification rather than efficient completeness; still, it earns a solid score for structure.

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

Completeness2/5

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

For a simple one-parameter mutation without output schema, the description is too minimal. It lacks context on the approval workflow, distinguishes poorly from sibling tools, and offers no return-value or state-change explanation, making it insufficient for reliable tool selection.

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?

The only parameter (purchase_order_id) has no description in the schema (0% coverage), and the tool description does not mention it either. The agent gets no help understanding the format, constraints, or semantics of the parameter beyond the type/required flags.

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 uses a specific verb ('submit') and resource ('purchase order') to convey the action, which is clear at a basic level. However, it does not distinguish from the closely related 'books_approve_purchase_order' or explain the scope of submission, so it stops short of full clarity.

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?

There is no guidance on when to use this tool versus alternatives like 'books_approve_purchase_order' or 'books_create_purchase_order'. No prerequisites, expected input state, or workflow context is provided, leaving the agent to guess.

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