Skip to main content
Glama

ADS Beast

list_proposals

Read-only

Change proposals waiting for a person (status pending by default), or their history. Each proposal shows what would change, why, and who proposed it.

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
limitNoProposals per page. A page is also cut to fit the response size limit; when the reply has has_more = true, call again with offset = next_offset.
offsetNoProposals to skip; use next_offset from the previous page.
statusNopending, approved, rejected, executed, expired or failed.pending
client_idNoOnly proposals for this client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the default view is the pending queue and that items carry a rationale and proposer, which is useful beyond the annotations, but it says nothing about ordering, whether the list is scoped to the caller's workspace/permissions, or what an empty queue means.

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?

Two short sentences with no waste, and the primary scope (pending queue) is front-loaded before the history variant. The second sentence about proposal contents is slightly tangential to invoking the tool but still earns its place given there is no output schema.

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?

For a read-only, fully documented, zero-required-parameter list tool this is nearly complete, and the sentence describing what each proposal contains compensates for the absence of an output schema. Only ordering and result-shape specifics are left unaddressed, which is minor here.

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 limit, offset, status and client_id are already fully documented including pagination via next_offset. The description only reinforces the default status value, which the schema already states, so it adds little meaning beyond the structured data.

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 a concrete resource (change proposals) and a precise scope: items waiting for a person, defaulting to the pending status, with the option to pull history instead. The verb is implied by the tool name rather than restated, and no sibling list_* tool is named, but the resource is specific enough that an agent can distinguish it from the other list_* tools without opening the schema.

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

Usage Guidelines3/5

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

The parenthetical "status pending by default" tells the agent the default behavior and implicitly that passing another status yields history, which is genuine usage context. However, there is no explicit when-to-use/when-not guidance, no mention of when to review history versus the pending queue, and no prerequisites or alternatives named.

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.