Zoho CRM + Books MCP Server

crm_semantic_field_search

Find Zoho module fields semantically related to a concept like 'status' or 'reason'—enter the module to retrieve matching field names, including custom fields.

Instructions

Semantic field search - find fields related to a concept (e.g., "disposition", "status", "reason")

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_name": "<module_name>",
      "concept": "<concept>"
    },
    "name": "crm_semantic_field_search"
  }
}

Input Schema

Name	Required	Description
`concept`	Yes	Concept to search for (e.g., "disposition", "status", "reason")
`module_name`	Yes	Name of the module
`include_custom_fields`	No	Include custom fields in search (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the high-level action and does not mention how the search is scoped (e.g., by module), what happens with include_custom_fields, or what kind of results are returned. There is no contradiction with annotations since none exist, but transparency is minimal.

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, well-structured sentence that immediately conveys the tool's function. It includes parenthetical examples that are useful without being verbose. Every word earns its place, making it an example of concise writing.

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?

Despite having a simple parameter set, the tool lacks an output schema and the description does not explain what the search returns (e.g., field names, labels, metadata). It also lacks usage guidance or behavioral context, leaving the agent to guess the tool's full capabilities. More details about result structure or search scope would be necessary for completeness.

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%, so the parameters are already well-documented. The description adds only examples of 'concept' values that duplicate the schema's own examples (e.g., 'disposition', 'status', 'reason'). It does not provide additional semantic meaning beyond the schema.

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 clearly states the tool's purpose: 'Semantic field search - find fields related to a concept' with concrete examples like 'disposition', 'status', 'reason'. It uses a specific verb ('find') and resource ('fields related to a concept'), and the term 'semantic' distinguishes it from literal search tools like crm_search_fields, though not explicitly.

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 given on when to use this tool versus alternatives such as crm_search_fields or crm_smart_field_discovery. There is no mention of scenarios where semantic search is preferable or exclusions, leaving the agent to infer usage from the name and description alone.

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

Deploy Server