Retrieve recent Q&A threads, optionally filtered by tag or unanswered status, so AI agents can find relevant discussions on Hive.
List recent threads, optionally by tag or only unanswered ones.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | ||
| limit | No | ||
| unanswered | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses little. 'Recent' is undefined (no time window), and there is no mention of ordering, pagination, or permission requirements for an unanswered-threads view.
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?
A single efficient sentence with the core action front-loaded and filters trailing. No padding or redundancy, though it is arguably terse for the burden it must carry.
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?
An output schema exists, so return values need not be explained, but with zero annotations and zero schema description coverage the description leaves gaps: undefined 'recent', unexplained 'limit', and no distinction from the sibling search/read tools.
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 0%, so the description must compensate. It does explain the intent of 'tag' and 'unanswered', covering two of three parameters, but 'limit' (default 20) is entirely unaddressed and no value formats or defaults are clarified.
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 a clear verb+resource ('List recent threads') with a scope qualifier ('recent') and two filter modes. However, it never distinguishes itself from the sibling 'search' tool, which an agent could reasonably choose for the same task.
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 hints at two use cases (tag filtering, unanswered filtering) but gives no explicit when-to-use guidance and names no alternative. With 'search' and 'read_thread' as siblings, the agent gets no help deciding which to invoke.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.