Skip to main content
Glama

List changes awaiting human approval

pending_changes
Read-only

List proposed changes to confirm-required slots waiting for human approval, so agents can see which updates have not been applied and require review before taking effect.

Instructions

List proposed changes to confirm-required slots that have NOT been applied.

Slots declared with "confirm" in the slot schema do not auto-apply a replacement or removal — the current value stands until a person approves. This is the queue of what is waiting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pending_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
user_idNodefault
agent_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

B3.4/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description explains the underlying mechanism: slots declared "confirm" do not auto-apply, and the current value stands until a person approves. That is real behavioral context an agent cannot get from the annotations, though nothing is said about pagination or ordering of the queue.

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?

Two sentences plus a short clarifying clause, front-loaded with the key constraint (NOT applied). The final sentence restates the queue idea already implied by the first line, a minor redundancy.

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 tool is simple and read-only, an output schema exists so return shape need not be described, and the confirm-slot semantics are covered. The remaining gap is parameter meaning, which the description leaves entirely to an undocumented schema.

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?

All three parameters (run_id, user_id, agent_id) have 0% schema description coverage and default values, and the description says nothing about how any of them scope the result. With no schema documentation and no compensating description text, an agent must guess whether run_id filters the queue or is required context.

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?

States a specific verb and resource ("List proposed changes to confirm-required slots") plus a negative scope ("that have NOT been applied"), which tells an agent exactly what comes back. It does not name the adjacent confirm_change/reject_change tools, so sibling differentiation is left implicit.

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 phrase "This is the queue of what is waiting" implies the use case (find items awaiting human approval before acting), but there is no explicit when-to-use rule, no mention of confirm_change as the follow-up action, and no prerequisites stated.

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