Skip to main content
Glama

List the AI agent's changes

list_changes
Read-onlyIdempotent

AI Agents: Use when the customer asks what the assistant changed in their systems, or to find a change to undo. Returns the newest proposed, applied, failed and undone changes, each with its before and after values and its id. Not for automation rules (use list_automations).

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many changes to return, 1 to 50.
systemNoOptional AI agent, by its system or connection name; all when left out.

Output Schema

NameRequiredDescriptionDefault
noticeNo
changesYes
manageUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"Optional: which AI agent, by the system's id from get_ai_agent_options or its name. Leave it out for all of them."New value: +"Optional AI agent, by its system or connection name; all when left out."
  2. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"Optional: which AI agent, by the system's id from get_ai_agents_info or its name. Leave it out for all of them."New value: +"Optional: which AI agent, by the system's id from get_ai_agent_options or its name. Leave it out for all of them."
  3. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"Optional: which AI agent, by the system's id from list_ai_systems or its name. Leave it out for all of them."New value: +"Optional: which AI agent, by the system's id from get_ai_agents_info or its name. Leave it out for all of them."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description's added value is the return shape: newest-first ordering, the four statuses, and per-change before/after values with ids. It does not explain how the limit interacts with the status mix or whether results are truncated, which keeps it below a 5.

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?

Three short sentences with the trigger and return contents front-loaded and the exclusion last; every clause carries routing or scope information. No filler or repetition of the title.

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?

With an output schema present, the description need not detail return values, and it still summarizes statuses and before/after payloads. The only real gap is behavior under the limit parameter (whether ordering guarantees the most recent N are kept across all statuses), which is not addressed.

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 100%, so limit and system are already documented in the schema, establishing a baseline of 3. The description adds only the implicit "newest" ordering and full unfiltered scope; it gives no extra semantics for the system filter or what happens when limit truncates.

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 ("list the AI agent's changes") and pins the scope to newest proposed, applied, failed and undone changes with before/after values and ids. It also explicitly excludes automation rules and names the sibling to use instead, so it is distinguishable without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("Use when the customer asks what the assistant changed in their systems, or to find a change to undo") plus a when-not with the named alternative list_automations. The agent can route between this and the automation-listing tool from the description alone.

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.

Resources