Search the CraftedTrust registry overlay for indexed MCP packages and servers. Filter by grade, certification, or scan type.
| Name | Required | Description | Default |
|---|---|---|---|
| grade | No | Filter by letter grade. Default: show all | |
| limit | No | Max results (1-50). Default: 10 | |
| query | Yes | Search term (name, URL, publisher) | |
| certified | No | Filter to certified servers only. Default: show all | |
| scan_type | No | Filter by scan type. Default: all |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It describes filtering but does not state whether the operation is read-only, safe, or if there are any destructive effects or rate limits. For a search tool, the implied behavior is non-destructive, but this is not explicitly confirmed, leaving uncertainty.
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 concise—two sentences that immediately state the purpose and key filter options. No redundant or wasted words. The structure is front-loaded with the primary action, making it easy for an agent to quickly understand the tool's function.
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?
Given five parameters, no output schema, and no annotations, the description is too sparse. It does not explain the search algorithm (exact match, fuzzy?), the result format, pagination behavior (though limit is a parameter), or default filtering when no parameters are provided. An agent would need more context to use the tool effectively.
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?
The input schema has 100% coverage, so each parameter is already documented. The description adds a paraphrased summary ('Filter by grade, certification, or scan type') but does not provide additional meaning or usage details beyond the schema. Baseline score of 3 is appropriate.
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 tool's purpose: searching the CraftedTrust registry overlay for MCP packages and servers. It uses a specific verb-resource combination ('Search ... registry overlay') and lists filterable attributes (grade, certification, scan type). This distinguishes it from sibling tools like check_trust, get_stats, and scan_server.
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?
The description implies usage: when you need to search and filter the registry. However, it does not explicitly state when to use this tool versus alternatives (e.g., check_trust for trust checks), nor does it mention any prerequisites or exclusions. The guidance is adequate but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, non-overlapping purpose: lookup trust scores, get ecosystem stats, trigger live scans, and search the registry.
All tool names follow a consistent verb_noun pattern (check_trust, get_stats, scan_server, search_registry).
With 4 tools covering core trust/security operations, the set is well-scoped and not excessive.
The set covers lookup, stats, scanning, and search; missing a tool for bulk listing or reporting, but the domain is well addressed.
