API Evangelist Conversations — recorded discussions with API practitioners (guest, company, YouTube/SoundCloud links).
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Free text over title, summary, tags, and body. | |
| page | No | ||
| sort | No | ||
| tags | No | Tag slugs; match any by default. | |
| limit | No | ||
| match | No | any | |
| fields | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must disclose behavioral traits. It only states the purpose but fails to mention read-only nature, pagination, sorting, or any side effects. The agent lacks critical behavioral context.
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?
Single sentence, concise and front-loaded with purpose. However, it could efficiently add more detail without becoming verbose.
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 or annotations; description is too sparse for 7 parameters. Lacks details on search behavior, result structure, and constraints, leaving agents underinformed.
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 only 29% (2 of 7 parameters described). The description adds no parameter-level information, failing to compensate for undocumented fields. Agents get minimal help understanding parameters like sort, match, or fields.
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 it finds conversations, specifically recorded discussions with API practitioners, including guest and company details. It distinguishes from sibling tools like find_videos or find_posts by focusing on conversations, though no explicit differentiation.
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 like find_videos or find_posts. Agents have no context on which tool to select for searching conversations vs other content types.
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.
