Skip to main content
Glama
Mipiti
by Mipiti

List Proposals

list_proposals

Review proposal and escalation outcomes on a threat model. Use it to poll a decision_request after a refused judgment and see when a person resolves it.

Instructions

List proposals and escalations on a model. Call this to poll the outcome of a proposal you raised, or of a judgment you were refused. Read-only; no side effects.

Statuses: proposed and applied_pending_review are open; accepted, rejected, reverted, superseded are closed. Kinds include add_component, remove_component, design_change, and decision_request: an escalation of a judgment this agent was refused. A 403 from update_finding, create_risk_acceptance, or decide_proposal carries an escalation_id; that escalation appears here as a decision_request. Poll it here until a person resolves it; do not retry the refused call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoOptional status filter (one of the values above). Empty (default) returns every proposal.
model_idYesID of the threat model.
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.75.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so excellently: it states 'Read-only; no side effects' directly. It also explains status semantics, kinds, and the escalation lifecycle, offering substantial behavioral context beyond the bare schema.

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?

The description is dense but efficiently organized: an opening summary, a clear call-to-action, then structured status/kind information. Every sentence adds useful guidance, and critical behavioral information is front-loaded.

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?

Given the output schema exists, the description need not explain return values. It covers purpose, triggering conditions, statuses, escalation behavior, and the no-retry directive, making it fully sufficient for an agent to use correctly.

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

Parameters4/5

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

The description enriches the status parameter by enumerating valid status values and explaining what open versus closed means. It also explains kinds including decision_request. However, the required server_version parameter is left undocumented in both schema and description, which prevents a perfect score.

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 clearly states a specific verb and resource: 'List proposals and escalations on a model.' It immediately connects the tool to polling outcomes of proposals or refused judgments, making its purpose unambiguous and distinguishable from decision-related siblings like decide_proposal and list_decisions.

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?

The description explicitly says when to call it: poll for a proposal outcome or a refused judgment. It even explains the escalation flow from 403 responses and instructs the agent to poll rather than retry, giving concrete, actionable usage guidance.

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

Deploy Server

Other Tools