Skip to main content
Glama

reject_protocol

Reject a pending protocol proposal with a reason to stop unwanted swarm behavior and keep governance decisions explicit.

Instructions

Reject a pending protocol proposal with a reason.

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": {
      "projectDir": "<projectDir>",
      "proposalId": "<proposalId>",
      "reason": "<reason>"
    },
    "name": "reject_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesReason for rejection
projectDirYesAbsolute path to the project directory
proposalIdYesID of the proposal to reject
reviewedByNoWho is rejecting (default: orchestrator)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Since no annotations are provided, the description must bear the full burden. It does not specify success or failure modes, nor does it mention any constraints on the provided 'reason' beyond its existence.

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 definition is a single, highly concise sentence where every word serves to define the tool's function and scope without any unnecessary fluff.

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 tool with clear naming and 100% parameter documentation, the description is very complete for invocation. However, the lack of behavioral context or defined failure states prevents a perfect score.

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?

With 100% schema coverage, the schema defines the necessary inputs (projectDir, proposalId, reason). The description adds minimal semantic value beyond this structured information, making the baseline score appropriate.

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 uses a specific verb ('Reject') and identifies the exact resource ('pending protocol proposal'), clearly distinguishing it from related actions like proposing or approving.

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 correctly implies the context (reject a pending proposal), but it lacks explicit guidance on when to use this tool versus, for example, simply changing the state of the proposal.

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