Skip to main content
Glama
Sign In

BitBasic

by com.bitbasic
OverviewDiscussionsAdmin

Governance proposals

governance-proposals
Read-onlyIdempotent

Governance proposals on one network or every one: the latest, those in one status (open for votes, opening soon, passed, rejected, other outcomes), or one proposal in full with its text, tally and (on Cosmos networks) how each validator voted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "governance-proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNoThe same as status "open". Default: the latest 10.
statusNoOnly proposals in this status, the same on every network: open (taking votes, soonest to close first), soon (opening soon), passed, rejected or other. Default: any.
networkNoA network slug from list-networks. Default: every network with governance (not with "proposal").
proposalNoOne proposal's number, for it in full (needs "network").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing what a full proposal contains (text, tally, per-validator votes on Cosmos networks) and that status filtering behaves the same across networks. It omits pagination, result limits and rate-limit behavior, which matters for a list tool.

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?

A single front-loaded sentence that enumerates the modes before the details, with zero filler. It is dense and reads as one long clause chain, but every phrase carries information.

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

Completeness4/5

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

With no output schema, the description usefully characterizes the return payload for the full-proposal case. Defaults and the network requirement live in the schema, so the combined picture is nearly complete; only pagination/result-size behavior for the list modes is unaddressed.

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

Parameters3/5

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

Schema coverage is 100% and the schema descriptions already explain the status enum, the open shortcut and the network dependency. The description reinforces the status vocabulary and explains what the proposal parameter yields, but adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

Names the resource (governance proposals) and the three retrieval modes: latest, filtered by status, or a single proposal in full. That is specific enough for an agent to know exactly what comes back, though it never contrasts itself with a sibling (none of the listed siblings covers governance, so the risk is low).

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

Usage Guidelines4/5

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

Effectively documents three call shapes and the conditions that select them: omit arguments for the latest, pass status/open to filter, pass proposal plus network for one proposal in full. The parenthetical '(needs "network")' states a prerequisite. It stops short of explicit when-not-to-use guidance, but there is no overlapping sibling to route away from.

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

All BitBasic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources