Skip to main content
Glama

Prior Ledger

accept_proposal

Reviewer tokens with review:accept only. Accept a proposal into the ledger. This is permanent: the entry can be superseded later but never removed. The commit names your token.

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

Input Schema

NameRequiredDescriptionDefault
pidYes
noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the required auth scope, states that the action is irreversible in the sense that the entry can be superseded but never removed, and notes that the commit records the caller's token (attribution). Annotations already cover the safety profile, so this added context is exactly the kind that matters for a mutation tool.

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?

Three short sentences, front-loaded with the access constraint and then the effect. Nothing is wasted, though the final line 'The commit names your token' is terse enough to be slightly ambiguous about what is actually recorded.

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?

Safety and irreversibility are covered and no output schema exists to explain, but for a two-parameter mutation the description leaves the only required input ('pid') and the optional 'note' entirely undefined. An agent can infer intent but not how to populate the call correctly.

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?

Schema description coverage is 0% and the description says nothing about either parameter: neither what 'pid' identifies (presumably a proposal id) nor what 'note' is used for or how it is stored. With two undocumented parameters, the description does not compensate for the schema gap.

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?

States a specific verb and resource ('Accept a proposal') plus the destination ('into the ledger'), which cleanly separates it from reject_proposal and submit_proposal by name alone. The permanence clause adds the consequence of the action, so an agent knows what it is committing to 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 description gives a hard prerequisite ('Reviewer tokens with review:accept only'), which usefully gates who may call it. However, it never says when to accept versus reject, nor whether review_proposal or proposal_status should be consulted first, so the usage decision is only implied.

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.