Zoho CRM + Books MCP Server

crm_create_role

Create a new role in Zoho CRM by supplying role data, establishing access permissions and organizational structure.

Instructions

Create a new role

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": {
      "role_data": "<role_data>"
    },
    "name": "crm_create_role"
  }
}

Input Schema

Name	Required	Description	Default
`role_data`	Yes	Role data

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

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 must carry the full burden of behavioral disclosure. It only states the action 'Create' without mentioning side effects, permission requirements, idempotency, or what happens to existing roles. This is slightly more informative than a tautology but still provides no behavioral traits beyond the verb.

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 concise sentence that is front-loaded and lacks fluff. However, its extreme brevity borders on under-specification, which slightly reduces the score from perfect since it provides minimal structure for the reader.

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?

For a creation tool with no annotations, no output schema, and a vague parameter schema, the description is severely incomplete. It omits what data is needed, what the role_data structure should be, how the operation affects existing data, and what the response will be. The description provides almost no context beyond the action itself.

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?

The schema describes the sole parameter 'role_data' as 'Role data', which is a tautology. The tool description adds no meaning about what role_data should contain (e.g., name, permissions, parent role). With nested objects true, the description fails to compensate for the schema's vagueness.

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 'Create a new role' clearly states the verb and resource, distinguishing it from sibling update/delete/get-role tools. However, it lacks context about what a 'role' entails in this CRM system and does not explicitly differentiate from other 'create' actions like crm_create_profile or crm_create_user.

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 such as crm_update_role or crm_create_profile. There are no prerequisites, no mention of required permissions, and no indication of whether this should be used before assigning roles to users.

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

Deploy Server