Skip to main content
Glama

Proposals

get_proposals
Read-onlyIdempotent

The Assembly’s proposals, live ones first: each with its state, text, exact on-chain actions (with any action to read carefully flagged), votes and deadlines, plus the rules for proposing and voting, and the Council of Models: its seats and newest recommendations. With an address, whether it has voted. Read-only.

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": "get_proposals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many settled proposals to list besides the live ones, 1 to 20. Default 10.
addressNoOptional: show whether this address has voted on each.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare read-only, open-world, idempotent, and non-destructive behavior, and the description adds substantive context: live-first ordering, the fields included, flagged on-chain actions, deadlines, Council of Models details, and the address filter’s effect. It redundantly repeats “Read-only,” but still provides meaningful behavioral detail beyond the annotations.

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 front-loaded with the resource and ordering, then efficiently lists the returned content. It is dense and includes a redundant “Read-only,” but most detail earns its place because no output schema exists.

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 supplies the main return contents, ordering, and address-filter behavior, while annotations cover safety and the schema documents parameters. It omits exact pagination/limit behavior and precise return structure, but is otherwise complete for a read-only listing tool.

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 description coverage is 100%, so both the limit and address parameters are already documented in the schema. The description restates the address filter’s effect and implies the live-versus-settled distinction, but adds no syntax, default, or other semantics 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 states a specific resource—the Assembly’s proposals—and specifies live-first ordering plus the returned contents. It is clear enough to distinguish from generic sibling tools like get_state, but it does not explicitly contrast itself with any sibling.

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?

The description explains what the tool returns but gives no when-to-use or when-not-to-use guidance and names no alternatives among the sibling tools. An agent can infer that this is the read path for proposals, but it must infer that entirely from the resource description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources