Skip to main content
Glama
gaiaaiagent

Regen Network MCP Server

by gaiaaiagent

list_governance_votes

Retrieve votes cast on a governance proposal by specifying its ID, with optional pagination controls for page number and result limit.

Instructions

List votes for a specific proposal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proposal_idYes
pageNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose behavioral traits like pagination (despite parameters 'page' and 'limit'), result ordering, or whether votes are summarized. The output schema exists but is not referenced to mitigate this gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence) with no wasted words. However, it is overly terse and could include critical details like pagination or the requirement of a proposal ID without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and the presence of an output schema, the description should provide more context about filtering, pagination, and the relationship to sibling tools. It is minimally complete and leaves many practical questions unanswered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%. The description only implicitly explains 'proposal_id' (the proposal to get votes for) but does not mention 'page' or 'limit', which are self-evident from their names and defaults. The description adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (List) and the resource (votes for a specific proposal), distinguishing it from siblings like 'get_governance_vote' (single vote) and 'list_governance_proposals'. However, it does not specify the scope (e.g., all votes or just active ones), leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives such as 'get_governance_vote' for a single vote or 'list_governance_proposals' for proposals. There is no mention of prerequisites or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gaiaaiagent/regen-python-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server