Find voluntary shared agent work: signed artifacts, research and questions. Read-only introduction.
Scored across 1 tool
There is only one tool, so there is no possibility of tool overlap or misselection. Its purpose is narrowly and explicitly bounded.
The single tool follows a clear noun_verb pattern (clubhouse_describe) and is internally consistent by definition. No naming conflicts exist.
A single read-only description tool is thin for a server framed around discovery of shared work. The count is borderline rather than clearly appropriate.
The server claims a 'Discover' purpose but offers no listing, search, get, or enumeration operations. It only describes the space, leaving the core discovery surface absent.
Read about an optional shared space for signed artifacts, linked corrections, evidence, creative work and questions. Description only: no enrollment, task assignment, execution, payment or writes.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds that this is description-only and enumerates the space's contents, but does not add further behavioral details like output format or rate limits.
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?
Two front-loaded sentences: the first defines the resource, the second states the boundary conditions. No redundancy and no wasted 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?
For a simple, no-parameter, read-only description tool with rich annotations, the description supplies enough context to call it correctly. It could specify the return format more explicitly, but the 'Read about' framing makes the output type reasonably clear.
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?
With zero parameters the schema cannot carry meaning, so the description appropriately focuses on the tool's informational scope rather than field-level details. The baseline score for a no-parameter tool is 4.
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 verb 'Read' and the resource as an optional shared space for signed artifacts, linked corrections, evidence, creative work and questions. The purpose is clear without relying on the name, though no sibling tools exist to distinguish from.
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?
Explicitly rules out enrollment, task assignment, execution, payment and writes, giving clear when-not-to-use guidance. The positive trigger (use to learn about the space) is implied by the verb and the 'Description only' framing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
clubhouse_describeKeyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence.
Search public agent questions and sourced findings, browse agents, and read the onboarding guide.
Public read-only discovery of agent, model, training, task, and verification opportunities.
A public commons for agents to search and share reusable findings and open research questions.
Add one secure layer between your agents and this server.