Skip to main content
Glama

Changes review

changes_review
Read-onlyIdempotent

Reviews recorded actions with their actual application dates, baseline and observation eligibility (the change-review method). Pending, failed and skipped actions are kept apart from measured results, and rolling snapshots are not presented as causal lift. Scoped to one selected account, optionally one action; paginated. responseMode=answer returns a report; evidence returns the data for broader tasks or several pages or accounts. No writes and no saved learning.

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": {
      "input": "<input>"
    },
    "name": "changes_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces them consistently with 'No writes and no saved learning'. It also adds behavior beyond the annotations: pending, failed and skipped actions are separated from measured results, and rolling snapshots are not presented as causal lift. That is useful methodological transparency, though permission or rate-limit behavior is unstated.

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?

The description is dense but front-loaded: the core action and method come first, then scoping, then the responseMode rule, then the safety statement. Individual sentences are long and clause-heavy, and the parenthetical '(the change-review method)' is doing light work, but there is no filler.

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 no output schema, the description carries the burden of explaining what comes back, and it does so by identifying the report content and the distinct answer-vs-evidence modes. It omits details such as pagination bounds and how the optional actionId narrows the review, which are minor gaps for a read-only review tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and already documents language, accountId and responseMode in detail, so the description only needs to add framing – which it does by explaining that evidence mode is for broader tasks, several pages or accounts, and that scope is one account with an optional single action. The limit, offset and actionId parameters gain no meaning from the description itself, keeping it below 5.

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?

The description states a specific verb and resource – reviewing recorded actions with application dates, baseline and observation eligibility – and frames it as 'the change-review method', which distinguishes it from siblings like findings_review or performance_diagnose. It stops short of explicitly naming an alternative tool, so a 4 rather than 5.

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 gives clear scope (one selected account, optionally one action, paginated) and a substantive rule for choosing responseMode: answer for a diagnostic or outcome review, evidence only for an explicitly requested extra deliverable or multiple accounts/pages. That is real when-to-use guidance, though it never names a sibling tool as the alternative for a different task.

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.