Skip to main content
Glama

Discard a pending change

reject_change

Discard a proposed change so the current value stands while preserving the proposal in audit history; requires approval to prevent silent review-queue clearing.

Instructions

Discard a proposed change. The current value stands. The proposal is kept as history — that someone proposed it is itself worth being able to audit. Needs approve, like confirm_change: an agent quietly discarding proposals would empty the review queue just as surely as approving them. decided_by is an optional note beside the authenticated caller.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "reject_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
user_idNodefault
agent_idNo
memory_idYes
decided_byNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, it explains that the current value remains unchanged and the proposal is retained for audit history. It also discloses the approval requirement and clarifies that decided_by is an optional note beside the authenticated caller.

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 purpose is front-loaded, and each sentence adds useful information about behavior, authorization, or parameters. There is no redundant restatement of the title or annotations.

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?

The description covers the mutation's safety profile, audit retention, and approval requirement well, and an output schema exists so return values need not be described. However, four of five input parameters remain unexplained despite zero schema coverage, leaving a meaningful completeness gap.

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% across five parameters, yet the description explains only decided_by. It does not clarify the required memory_id or the roles of run_id, user_id, and agent_id, so it does not compensate for the missing schema documentation.

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 states a specific action and resource: discard a proposed change while the current value stands. It distinguishes the operation from confirm_change by explaining the shared approval requirement and the review-queue consequence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly implies when to reject rather than apply a proposal, and names confirm_change as the comparable path. It lacks an explicit sentence such as 'use confirm_change to apply the proposal,' but the context is strong enough for correct tool selection.

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