Get a detailed trust and security report for one indexed tool by slug: publisher verification, permissions requested vs actually needed (with the overreach highlighted), injection-scan verdicts on the tool description, and the trust score interpretation.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Tool slug, e.g. 'github-mcp'. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Get' signals read-only retrieval, and the description discloses meaningful outputs: publisher verification, permission overreach, injection-scan verdicts, and trust score interpretation. It does not mention authentication or failure behavior, but that is a minor gap for a report retrieval tool.
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?
One well-structured sentence front-loads the operation and resource, then uses a colon-delimited list to convey report contents without unnecessary words.
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 an output schema present to document the return shape, the description adequately covers what the tool does, which input it needs, and what the report contains. The single-parameter invocation is fully supported.
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 coverage is 100%, and the slug parameter already includes an example. The description only adds that the slug identifies an indexed tool, which is useful but does not meaningfully augment the 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?
States the exact operation (get), the resource (detailed trust/security report), the selection method (by slug), and enumerates report contents. This makes it clearly distinct from siblings compare_tools and find_solutions.
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?
Clear context: this is for obtaining a trust/security report on one indexed tool identified by slug. The singular by-slug framing implies it is not for comparing tools or finding solutions, though it does not explicitly name those alternatives.
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 distinct purpose: find_solutions handles natural-language discovery, compare_tools performs side-by-side comparisons, and get_trust_report provides deep single-tool security analysis. There is no overlap or ambiguity between them.
All three tools follow a consistent verb_noun snake_case pattern: compare_tools, find_solutions, get_trust_report. The naming clearly indicates the action and target.
Three tools is on the low end but within the acceptable range and each tool earns its place for the gateway's focused scope. It may feel slightly thin for a broader discovery platform, but it is not excessive or trivial.
The set covers the core workflow: discover solutions, compare options, and retrieve trusted security details. A minor gap is the lack of an explicit catalog-browsing or listing tool, but find_solutions effectively addresses most discovery needs.