Skip to main content
Glama

List decision changes

list_decision_changes
Read-onlyIdempotent

Drain decisions whose state changed, since a cursor. Call with no since to start from now (returns an empty set + the current cursor); then call repeatedly with the returned cursor to get changes in order. Includes reversals (dropped/superseded). Read-only; poll this on a schedule.

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_decision_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax changes to return (1–200, default 50).
sinceNoOpaque cursor from a previous call. Omit on the first call to start from now (no backfill).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses the initialization behavior (empty set plus current cursor, no backfill), the ordering guarantee, the fact that reversals such as dropped/superseded decisions are included, and a recommended polling cadence — all real behavioral context an agent needs to drive the cursor loop.

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?

Four short sentences, front-loaded with the core action and followed by the call sequence, inclusions, and cadence. No filler and nothing repeated from the schema verbatim.

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?

For a two-optional-parameter read tool with no output schema, the description covers initialization, iteration, ordering, and scope of returned changes. It does not sketch the shape of an individual change record, a minor gap given there is no output schema to fall back on.

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 100% and both parameters are documented with defaults and ranges, so the schema carries most of the load. The description adds value by explaining the multi-call cursor protocol — that the returned cursor from one call feeds the `since` of the next — which is meaning beyond the field descriptions.

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 names a specific verb and resource ('Drain decisions whose state changed, since a cursor') and frames the tool as an incremental change feed, which an agent can immediately distinguish from a one-shot query tool like query_decision 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 Guidelines4/5

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

It gives concrete usage sequencing: call with no `since` to initialize from now, then call repeatedly with the returned cursor, and poll on a schedule. It does not name an alternative (e.g. query_decision) or state when not to use this tool, so it stops short of a 5.

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