Skip to main content
Glama

Approve a pending change

confirm_change

Approve a proposed change to a confirm-required slot and apply linked changes, with override for intended constraint overlaps such as bridging.

Instructions

Approve a proposed change to a confirm-required slot, applying it together with any changes linked to it. Needs the approve capability (admin and member roles; agents lack it, so an agent can't approve its own proposal). The approver recorded is the authenticated caller; decided_by is an optional note. If approving would break a declared constraint (e.g. two anticoagulants current) it is refused; pass override=true when the overlap is intended, such as bridging.

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

Input Schema

NameRequiredDescriptionDefault
run_idNo
user_idNodefault
agent_idNo
overrideNo
memory_idYes
decided_byNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the required `approve` capability, that agents cannot approve their own proposals, that the approver is the authenticated caller, and that constraint violations cause refusal unless overridden. The mutation described is consistent with readOnlyHint=false and destructiveHint=false, so no contradiction.

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 dense sentences that front-load the action, then prerequisites, then the override rule. No filler, though the parenthetical clinical example and the agent-role aside add length that a shorter form could carry.

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

Completeness5/5

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

An output schema exists, so return values need not be explained. For a non-idempotent mutation, the description covers who can call it, who gets recorded, what gets applied, and how refusals and overrides work — enough for correct invocation.

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 full burden. It explains `override` (constraint bypass) and `decided_by` (optional note vs. recorded approver) well, but leaves run_id, user_id, agent_id and the required memory_id undocumented.

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 ('Approve a proposed change to a confirm-required slot') plus the cascade behavior ('applying it together with any changes linked to it'). The action is unambiguously distinct from the sibling reject_change without needing to open either schema.

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?

Gives clear conditions for use and the override escape hatch ('pass override=true when the overlap is intended, such as bridging'), plus the prerequisite capability and the agent exclusion. It stops short of explicitly naming reject_change or stating when not to approve, but the context is strong enough to act on.

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