zoho_crm_js_examplesRetrieve ranked Zoho CRM JavaScript SDK examples filtered by topic, tag, or tier, helping you find the right code patterns for your integration tasks.
Return ranked Zoho CRM JavaScript SDK examples from the local curated knowledge pack.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | ||
| tier | No | ||
| query | No | ||
| topic | No | ||
| max_results | No | ||
| canonical_key | No | ||
| include_variants | No |
Changes observed during successful MCP inspections.
v0.1.1-beta.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does disclose that the tool returns ranked examples from a local curated knowledge pack, implying a read-only, offline retrieval operation. However, it does not explain ranking criteria, return format, or any limitations beyond the basic retrieval behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or redundancy. It efficiently communicates the action, subject, and data source without repeating the title unnecessarily.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 7 parameters, no output schema, and no annotations, the description is too minimal to be contextually complete. It fails to explain how parameters affect results, what output to expect, or how this tool relates to sibling examples tools. Significant operational context is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not compensate for any of the 7 parameters. It mentions 'ranked' and 'examples' but provides no meaning for tag, tier, query, topic, max_results, canonical_key, or include_variants. An agent would have no semantic grounding for constructing a correct request.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Return'), the resource ('ranked Zoho CRM JavaScript SDK examples'), and the source ('local curated knowledge pack'). It also inherently distinguishes itself from the Deluge-focused sibling tools by naming the JavaScript SDK.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus alternatives such as deluge_examples. The description implies it is for JavaScript SDK examples, but it does not explicitly state the appropriate context, exclusions, or how it differs from sibling retrieval tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.