Skip to main content
Glama

Prior Ledger

proposal_status

Read-only

Whether a proposal is pending, accepted (with its ledger id) or rejected (with the steward's note).

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": {
      "pid": "<pid>"
    },
    "name": "proposal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the three possible outcomes and the extra payloads attached to two of them (ledger id on accepted, steward's note on rejected), which is exactly the behavioral detail an agent needs. It does not cover behavior for an unknown or malformed pid, which keeps it below a 5.

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?

One compact sentence with no filler, and the most important fact (the three outcomes) is front-loaded. It reads as a sentence fragment rather than a complete definition, but nothing in it is wasted.

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?

With no output schema, the description does the important work of enumerating return states and their associated fields, which suits a one-parameter read tool. It still leaves the identifier semantics and the failure case for a nonexistent proposal unexplained, so it is adequate but not complete.

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

Parameters2/5

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

The single parameter 'pid' has no schema description at all (0% coverage, only the title 'Pid'), so the description carries the full burden of explaining it and says nothing. It never states that pid is the proposal identifier, nor its expected form or whether it refers to an on-ledger id. With schema coverage this low the description should have compensated.

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 description identifies the resource (a proposal) and the state dimension it reports (pending / accepted / rejected), so the intent is inferable. However, it is a noun-phrase fragment with no verb ('returns the status of...'), and it does not distinguish this read from siblings such as review_queue or get_entry that could also surface proposal state.

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 explicit when-to-use guidance, no mention of when to prefer this over review_queue or get_entry, and no note about checking status after submit_proposal or before accept_proposal/reject_proposal. Usage is only implied by the word 'proposal'.

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.