Skip to main content
Glama

List rule-change proposals

list_proposals
Read-only

Rule-change proposals with their status and the human's decision note.

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

Input Schema

NameRequiredDescriptionDefault
statusNoOnly proposals in this state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the useful detail that each proposal carries a status and a human decision note, which matters for interpreting results, but says nothing about ordering, pagination, or how rejected items appear.

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 short sentence with no filler, but it is a noun phrase rather than a descriptive statement, so the core action is not front-loaded. Nothing is wasted; more is simply missing.

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

Completeness3/5

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

For a one-parameter read-only list tool this is minimally sufficient, especially since the description names two returned fields in the absence of an output schema. Ordering, pagination, and what a proposal contains beyond status and decision note remain unexplained.

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 single enum parameter 'status' is fully documented in the schema, so the description need not repeat it. The phrase 'with their status' refers to returned data rather than the filter and risks mild confusion, but it does not add real parameter meaning.

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

Purpose3/5

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

The fragment 'Rule-change proposals with their status and the human's decision note' identifies the resource (rule-change proposals) and hints at returned fields, but omits an explicit verb and never states that this is a listing operation. It also does nothing to separate it from nearby list_requests or get_changes beyond the noun 'proposals'.

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?

There is no when-to-use guidance at all: no mention of when to prefer this over get_changes or list_requests, and no hint that the status filter can narrow results. The agent must infer everything from the name.

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