Skip to main content
Glama

What moved in the agent record

agent_changes
Read-onlyIdempotent

What moved in the agent record, across every agent, since a date. The counterparty check answers what is true about one address NOW; this answers what changed, for all of them, which is the question anybody holding a list asks next. One row per FIELD that moved, not per address: an agent whose dealings and concentration both moved is two facts, and folding them would make you diff the answer to work out what was meant. Roughly one agent in five moves on an ordinary day, out of about 2,900 tracked. A day with no row for an address is a day it did not move, never a day nobody looked. The record began on a date and from says which: asking for anything earlier answers from there rather than pretending nothing happened. Needs a key and the agents.changes capability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 1,000, maximum 5,000. Read `capped` before concluding you have it all.
sinceNoAn ISO date, such as 2026-10-01. The last seven days if you leave it out.
addressNoOne address, where you want its movement rather than everybody’s.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoThe first day held at all. There is nothing before it because the feed began when it began.
countYesRows IN THIS ANSWER, which is one per field that moved and not one per agent. Where `capped` is true it is the page size and not the total, so it is a floor on how much moved and never the whole of it.
itemsYesaddress, day, field, was, now, and the path of that agent’s full check.
sinceYesThe day this answer starts from, read back so a clamp is visible.
cappedNoTRUE where the page came back full, so ask again with an `offset`; FALSE means nothing moved after these rows in the window asked for, so the feed is complete rather than merely begun. A cap is not a count.
limitsYesWhat this answer cannot tell you. Quote it with the numbers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / capped / description
      Previous value: -"The page was full, so there may be more. A cap is not a count."New value: +"TRUE where the page came back full, so ask again with an `offset`; FALSE means nothing moved after these rows in the window asked for, so the feed is complete rather than merely begun. A cap is not a count."
  2. Changed1 schema field changed
    • addedOutput schema / properties / count / description
      Added value: +"Rows IN THIS ANSWER, which is one per field that moved and not one per agent. Where `capped` is true it is the page size and not the total, so it is a floor on how much moved and never the whole of it."
  3. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources