Skip to main content
Glama

proposal_list

Read-onlyIdempotent

Lists every recorded proposal in creation order, including rejected ones, so you can retrieve proposal IDs for gate checks or prior attempts.

Instructions

List every recorded proposal in creation order, rejected ones included, with id, parent, version, prediction, playbook version and a not_confirmed flag. Use it to find a proposal_id for gate_check or a prior attempt; use ledger_history for adoptions and the base chain. Read-only. Returns an array.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "config": "<config>"
    },
    "name": "proposal_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesPath of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • addedInput schema / properties / config / description
      Added value: +"Path of the scenario YAML file on the server host, absolute or relative to the server's working directory, for example `scenario.yaml`. It selects the workspace; a server started with --config rejects any other path."
  2. First observedv0.1.7

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "Read-only" earns no credit as new information. What the description does add beyond annotations is substantive: ordering guarantees, inclusion of rejected proposals, a not_confirmed flag, and the return shape ("Returns an array"). It stops short of noting whether results can be truncated for very large histories, which is the only remaining gap.

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

Conciseness5/5

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

Two sentences, zero filler. Scope and return fields come first, then routing guidance, then a short safety/return note. Nothing is repeated and nothing could be cut without losing information.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does it: it lists the fields returned and states the array shape. Combined with a fully documented parameter and complete annotations, an agent has everything needed to call this correctly.

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?

With a single parameter at 100% schema description coverage, the schema already fully documents the config path, including the server-startup constraint on alternate paths. The description says nothing about config at all, so it adds no meaning beyond the schema. Baseline 3 applies.

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

Purpose5/5

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

The description uses a specific verb ("List") on a specific resource ("proposal") and pins down scope: every recorded proposal, in creation order, rejected ones included. It even enumerates the returned fields, so an agent can distinguish it from ledger_history and proposal_create without opening a schema.

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

Usage Guidelines5/5

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

It states the concrete use case ("find a proposal_id for gate_check or a prior attempt") and names the sibling to use instead for a different need ("use ledger_history for adoptions and the base chain"). This is explicit when-to-use plus an explicit alternative, which is the top of the scale.

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