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

Zoho CRM + Books MCP Server

by Mgabr90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

crm_get_notes

Fetch notes for a specific Zoho CRM record by specifying its module and record ID.

Instructions

Get notes for a specific CRM record

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": {
      "module": "<module>",
      "record_id": "<record_id>"
    },
    "name": "crm_get_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
moduleYes
per_pageNo
record_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention pagination, return format, authentication requirements, or any side effects. The description is purely a high-level statement with no additional behavioral context.

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

Conciseness3/5

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

The description is a single sentence with no waste, but it is under-specified, lacking essential usage details. While concise in length, it does not serve the agent adequately, making it not 'appropriately sized' for the tool's complexity.

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

Completeness1/5

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

Given the tool has 4 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain how to identify the record, handle pagination, or interpret results, leaving the agent with insufficient context to invoke the tool correctly.

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 coverage is 0%, and the description does not explain the module, record_id, page, or per_page parameters. The phrase 'specific CRM record' implies record_id but omits module and pagination semantics. Description fails to compensate for the lack of schema documentation.

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 'Get notes for a specific CRM record' clearly states the action (get notes) and the target resource (CRM record). It distinguishes from siblings like crm_get_tasks and crm_get_attachments, though it could be more explicit about requiring module and record_id.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, such as knowing the module and record_id, nor does it compare with similar retrieval tools like crm_get_timeline or crm_get_attachments.

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