Search contacts by name, email, or company ID. Filter by active status and set page size up to 200 results per page.
Search contacts by name, email, or company. Max 200/page.
| Name | Required | Description | Default |
|---|---|---|---|
| searchTerm | No | Search term for contact name or email | |
| companyID | No | Filter by company ID | |
| isActive | No | Filter by active status (1=active, 0=inactive) | |
| page | No | ||
| pageSize | No | Max 200 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only says 'search' implying read-only but does not explicitly state non-destructive behavior. Lacks details on pagination limits beyond 'Max 200/page', no mention of data freshness or other traits.
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?
Two short sentences, no filler. Efficient but could benefit from a structured breakdown of search criteria.
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?
No output schema; description covers search action and pagination limit but lacks detail on response format or default behavior. Adequate for a simple search tool but not fully comprehensive.
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 80%; description adds 'by name, email, or company' but that is already captured by searchTerm and companyID descriptions. Minimal additional value beyond schema.
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?
Description clearly states 'Search contacts by name, email, or company' with specific verb and resource. Although sibling search tools exist, the name and description sufficiently differentiate this tool for contact searches.
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?
No guidance on when to use this tool versus alternatives among the many search siblings. Does not specify prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/asachs01/autotask-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server