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_blueprint_metadata

Retrieve blueprint metadata from Zoho CRM to understand process flows, states, and transitions for automating workflows.

Instructions

Get blueprint metadata

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description must convey behavior. It only states 'Get', implying a read-only operation, but gives no information about return format, data scope, authentication needs, or side effects.

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

Conciseness2/5

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

The description is a short phrase with no filler, but it is under-specified. While it is concise in length, it sacrifices essential clarification, making it an unhelpful placeholder rather than a well-structured, informative description.

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?

With no parameters, no output schema, and no annotations, the description alone must make the tool understandable. It fails to explain what 'blueprint' refers to in the CRM context, leaving the tool's purpose and return value ambiguous.

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 has zero parameters, so the baseline is 4. The description does not need to add parameter meaning, and the empty schema indicates no input is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource structure ('Get blueprint metadata'), which distinguishes it from siblings since no other tool mentions 'blueprint'. However, 'blueprint' is not defined, leaving the purpose vague—users cannot infer what this metadata represents.

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. The description does not mention any context, prerequisites, or exclusions, and does not reference sibling tools like crm_get_pipeline_metadata or crm_get_metadata_summary.

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