search_conversations
Search CRM conversations
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| contactId | No |
0nMCP — Universal AI API Orchestrator
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.4/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 behavioral traits. 'Search' implies a read-only operation, but it does not disclose pagination, result limits, required permissions, or any side effects. The description adds no behavioral context beyond what the tool's name suggests.
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 concise and free of fluff, but it is under-specified. It is a single short phrase that does not provide enough detail to be appropriately sized for the tool's complexity. While every word earns its place, the overall content is insufficient.
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?
With two parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain the purpose of parameters, expected return values, or any operational context. This tool is not adequately documented for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has two parameters (limit, contactId) with 0% coverage from the description. The description does not explain the meaning, format, or behavior of these parameters. Since schema descriptions are absent and the description offers no compensation, the agent has no guidance on how to use these parameters correctly.
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 'Search CRM conversations' clearly identifies the action (search) and the resource (CRM conversations). It is distinguished from sibling tools like search_contacts and search_opportunities by the resource type. However, it lacks any additional scope or filtering context, so it doesn't fully meet the 5-level bar.
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 gives no guidance on when to use this tool versus alternatives. It does not mention criteria, prerequisites, or any exclusions. The sibling list contains similar search tools, but no comparative or situational context is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.1/5.0
Disambiguation4/5
Most tools have distinct actions (create/get/update/search for contacts, opportunities, etc.). However, send_email overlaps with send_message which explicitly supports email, and verify_service is an outlier unrelated to the CRM-focused tools.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_contact, get_pipelines, send_message). The naming is predictable and uniform across the entire set.
Tool Count3/5
17 tools is at the heavy end for a CRM-focused server, and the 'Universal AI API Orchestrator' name suggests broader capabilities than the actual tool set. The count is not extreme but feels slightly over-scoped for what is offered.
Completeness3/5
Contact and opportunity management cover create/read/update/search with additional note/tag features, but there are no delete operations for contacts or opportunities, and appointment creation is missing. The verify_service tool adds an unrelated capability, leaving some CRM lifecycle gaps.