Issue a tamper-evident governance certificate attesting an API passed a named ruleset at a profile threshold. A SHA-256 fingerprint lets anyone re-verify it.
| Name | Required | Description | Default |
|---|---|---|---|
| api | Yes | The API description being attested or verified. String or parsed object. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It adds useful context about tamper-evidence and re-verifiability, but it does not disclose whether issuing the certificate persists state, requires authorization, or what the response contains. For a credential-issuing action, this is under-disclosed.
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 two sentences with no filler. The first sentence front-loads the core action and conditions, and the second adds the key self-verification property. Every sentence earns its place.
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?
Although the single-parameter schema is simple, the description refers to a 'named ruleset' and 'profile threshold' that are absent from the schema, so an agent cannot tell whether those are additional properties or inferred from the API description. With no output schema and no annotations, the issuance and re-verification flow is also under-specified.
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 schema already describes the only parameter, 'api', at 100% coverage, so the baseline is 3. The description does not add meaningful parameter detail and, in fact, introduces 'named ruleset' and 'profile threshold' concepts that are not present in the schema, leaving some ambiguity about what can actually be passed.
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 uses a specific verb ('Issue') and names a precise artifact ('tamper-evident governance certificate'), along with the conditions ('passed a named ruleset at a profile threshold') and the integrity mechanism ('SHA-256 fingerprint'). It is clearly distinct from sibling verify_certificate because this tool issues rather than verifies.
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 the use case: certify an API after it passes a ruleset. The fingerprint sentence hints at a separate re-verification action, but it never explicitly names verify_certificate or says when to prefer certify_api over validate_api or audit_pipeline. No exclusions, prerequisites, or alternative routing are provided.
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.
Most tools have distinct purposes with clear descriptions, reducing ambiguity. However, some overlap exists between search tools like 'find_posts' and 'search_api_evangelist', though they target different scopes (stories vs. unified search). Overall, an agent can reasonably differentiate them.
The majority of tools follow a verb_noun pattern (e.g., find_areas, get_post), but several use noun_noun or inconsistent prefixes (e.g., api_coverage, company_gaps, insights_adoption). This inconsistency can confuse pattern recognition, though the pattern is still readable.
With 56 tools, the server is overloaded for a typical MCP context. While the domain is broad, the sheer number risks agent confusion and selection errors. Calibration suggests 25+ tools are excessive, and this server far exceeds that threshold.
The tool set covers a wide range of API governance, search, analysis, and generation tasks. There are no obvious dead ends for navigating the API Evangelist network, though some areas (e.g., direct API creation) are intentionally out of scope. Minor consolidation could improve efficiency.
