search_services
Search the directory of reviewed agent services by name/URL, filter by kind, and sort.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| kind | No | ||
| sort | No |
vouchtrail
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of explaining behavior. It indicates a read-only search operation and mentions filtering and sorting, which is transparent enough for a safe operation. However, it does not disclose details like result format or pagination.
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, concise sentence that front-loads the main action and covers the key aspects (search, filter, sort) with no redundant words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is relatively simple with optional parameters and no output schema. The description explains the operation and parameter roles, but it does not mention the return format or provide context on related tools, leaving some gaps for a complete understanding.
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 schema has no parameter descriptions (0% coverage), so the description must explain the parameters. It does: 'by name/URL' maps to q, 'filter by kind' maps to kind, and 'sort' maps to sort. This adds meaning beyond the bare schema types and enums.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/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: searching a directory of reviewed agent services by name/URL, with filtering and sorting. It uses a specific verb ('search') and resource, and is distinct from sibling tools like get_service and get_verdict.
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 the sibling tools. The description only explains what the tool does, not when to choose it over get_service or get_verdict, or any exclusions.
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
A3.6/5.0
Disambiguation2/5
get_service and get_verdict both return verdicts with evidence, differing only in lookup (numeric id vs. unspecified). An agent could easily confuse which one to use, especially since get_verdict does not specify its input. search_services is distinct.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: get_service, get_verdict, search_services. Both 'get' verbs are for retrieval and 'search' for discovery, making the naming uniform and predictable.
Tool Count5/5
3 tools is within the ideal 3-15 range for a focused service. Each tool serves a clear role in retrieving verdict data or searching the directory, with no redundancy in count.
Completeness4/5
For a read-only service, the surface covers search and retrieval of verdicts and evidence. The only minor gap is that get_verdict and get_service are redundant, and there is no explicit 'list all' but search covers that. No major lifecycle gaps exist.