Skip to main content
Glama

Prior Ledger

reject_proposal

Destructive

Reviewer tokens with review:reject only. Decline a proposal. The note is shown to the proposer.

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>",
      "note": "<note>"
    },
    "name": "reject_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidYes
noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is covered. The description adds two things the annotations cannot: the required authorization scope and the fact that the note is surfaced to the proposer, which affects how the note should be written. It does not say what happens to the proposal's state or whether the action is reversible.

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 with the authorization constraint front-loaded and no filler. The phrasing "Reviewer tokens with review:reject only" is compressed to the point of being slightly ambiguous, which keeps it from a 5.

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?

For a destructive two-parameter mutation with no output schema, the definition covers permission, action, and note visibility, but omits the post-condition (what state the proposal enters) and what the caller receives back. Adequate but not complete.

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 coverage is 0%, so the description must carry parameter meaning. It explains the note's audience (visible to the proposer), which is genuine semantic value, but leaves pid completely undefined beyond what its name implies.

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?

"Decline a proposal" is a specific verb+resource that clearly contrasts with the sibling accept_proposal. The preceding sentence establishes the caller context (reviewer tokens with review:reject). It stops short of explicitly naming the sibling it is not, so a 4 rather than a 5.

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 supplies the key precondition for use (a reviewer token carrying review:reject), which tells an agent when this call will succeed. It gives no explicit condition for choosing rejection over acceptance or requesting changes, and no note about what state the proposal must be in.

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.