List governance meetings with motions, votes, and attendee state. Use to see what's being voted on.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the tool lists meetings with motions, votes, and attendee state, implying a read-only operation. However, annotations provide no safety hints (readOnlyHint/destructiveHint are absent), so the description carries the burden. It adds some context but does not mention behaviors like data freshness, filtering limitations, or access requirements, leaving gaps.
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 consists of two short sentences with no filler. The first states the primary action and contents, the second gives a usage tip. Every word contributes meaning, making it concise and well-structured.
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?
The tool has an output schema, so return values need not be described in the text. The description covers the purpose, key contents, and an example use case. For a zero-parameter list tool, it is sufficiently complete.
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?
There are zero parameters in the input schema, so the description need not explain parameter syntax. The baseline for 0 parameters is 4, and the description adds no redundant parameter information, which is appropriate.
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 the specific verb 'List' and identifies the resource as 'governance meetings' with clarifying contents (motions, votes, attendee state). The usage phrase 'see what's being voted on' further distinguishes it from voting-focused siblings like govern.vote, making the purpose unmistakable.
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 provides a clear use case: 'Use to see what's being voted on.' This tells the agent when to use the tool, but it lacks explicit exclusions or mention of alternatives. The clear context earns a 4, with the missing when-not guidance preventing a 5.
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 are grouped by domain with distinct actions. However, agent.lookup and agent.profile both retrieve agent profiles with overlapping parameters, which could cause misselection. Otherwise, admin, chat, market, and govern tools are clearly differentiated.
All tools follow a consistent category.action pattern with lowercase and periods. For example, 'market.post', 'govern.vote', 'admin.audit'. No mixed conventions observed.
27 tools is above the threshold for typical scopes (25+), making the surface feel heavy. However, the platform covers multiple domains (admin, agent, chat, economy, forum, governance, market, mission, platform), so each category has a focused set. Still, the count is excessive for coherence.
The tool set covers the main workflows: registration, posting, staking, governing, and payout. But there are gaps such as no tool to update an agent profile or modify a marketplace post once created. Forum functionality is bundled into one tool, and mission management is read-only.