Skip to main content
Glama
Sign In

Zoho_crm

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Zoho List Modules

zoho_list_modules
Read-onlyIdempotent

List all available modules in Zoho CRM.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zoho_list_modules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoError code if connection not available
messageNoError message if connection not available
modulesNoList of available modules in Zoho CRM

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error code if connection not available",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message if connection not available",
+      "type": "string"
+    },
+    "modules": {
+      "description": "List of available modules in Zoho CRM",
+      "items": {
+        "description": "Module information object",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

TDQS

A3.7/5.0
Behavior2/5

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

The description adds no behavioral context beyond the annotations, which already declare the operation as read-only, idempotent, and non-destructive. It does not mention specifics like return format, ordering, or that only module names are returned, offering no incremental transparency.

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?

The description is a single concise sentence, 'List all available modules in Zoho CRM,' with no redundant or extraneous words. It is front-loaded with the action verb and resource, making it easy to parse.

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

Completeness5/5

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

Given the tool's trivial nature, zero parameters, and the presence of an output schema, the description is sufficiently complete. It conveys the core function without needing additional explanation about return types or behavior, which the output schema likely covers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema is fully covered and the baseline score is 4. The description does not need to add parameter semantics, and it correctly omits any parameter-related details.

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 clearly states the tool lists all available modules in Zoho CRM, using a specific verb ('List') and resource ('modules in Zoho CRM'). This distinguishes it from sibling tools like zoho_list_records, which list records instead.

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?

The description provides no guidance on when to use this tool versus alternatives such as zoho_list_records or zoho_search_records. It only states what it does, leaving the agent to infer usage context from the tool name alone.

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

All Zoho_crm toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources