Skip to main content
Glama

ADS Beast

reject_proposal

Reject a pending proposal with a short reason. Returns the proposal id and its new status.

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

Input Schema

NameRequiredDescriptionDefault
reasonNo
proposal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so mutation semantics are partly covered. The description adds that this is a state transition to a new status and names the returned fields, which is genuinely additive since no output schema exists. It omits whether rejection is permanent or reversible and any permission or rate-limit considerations.

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 short sentences, front-loaded with the action and followed by the return value. No filler, hedging, or redundancy.

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

Completeness4/5

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

For a simple two-parameter mutation, the description covers the action, the precondition, and the return shape in lieu of an output schema, while annotations cover the safety profile. The remaining gap is minor: it does not describe failure behavior for non-pending or unknown proposal ids.

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 description coverage is 0%, so the description carries the burden. It tells the agent that the call takes a 'short reason' and implies the proposal is identified by id, which adds a mild length/quality hint beyond the bare types. It does not clarify that 'reason' is optional in the schema, nor give any format guidance for proposal_id.

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?

The description gives a specific verb and resource ('Reject a pending proposal') plus a state precondition ('pending'), which is enough to distinguish the operation from a generic update. It stops short of explaining what a proposal is or what rejection means in the broader workflow, so it falls just short of 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 word 'pending' implies a precondition (only proposals in a pending state can be rejected), which is useful implied guidance. However, there is no explicit statement of when to reject versus pursue another action, no mention of required permissions or roles, and no note about whether the action can be undone.

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.