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

Zoho CRM + Books MCP Server

by Mgabr90
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

crm_create_user

Create a new user in Zoho CRM with user data, automating user provisioning for streamlined access management.

Instructions

Create a new user

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": {
      "user_data": "<user_data>"
    },
    "name": "crm_create_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_dataYesUser data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior1/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. The description only says 'Create a new user' with no information about side effects, permissions, required fields, uniqueness constraints, or what happens after creation. This is a significant gap for a mutation tool.

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 extremely short (3 words) with no wasted text, but it essentially restates the tool name and provides no substantive information. It is under-specified rather than appropriately concise, so it does not fully earn its place.

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?

This tool has a nested object parameter ('user_data') and no output schema, yet the description gives no details about the structure of the data, expected fields, or behavior. The description is completely inadequate for an agent to understand how to invoke this tool correctly.

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% (the single parameter 'user_data' has a description, albeit vague). The tool description adds no additional meaning beyond the schema, but the baseline for high coverage is 3, and the description does not mislead.

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 states a specific verb ('create') and resource ('user'), clearly indicating the tool's purpose. While it does not explicitly compare with sibling tools, the resource 'user' is distinct among the many create_* tools in the sibling list, so the purpose is clear without ambiguity.

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. There is no mention of prerequisites, use cases, or exclusions, leaving the agent to infer context solely from the tool name.

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