Skip to main content
Glama

list_ai_modified_records

Read-only

List records that AI changed using the platform AI record activity log, showing table, record, and updated fields. Filter by table or date range, or return per-table counts.

Instructions

List records that were changed by AI (Otto / Now Assist, AI agents) using the platform AI record activity log (sys_ai_record_activity): table, record and which fields AI updated. Filter by table and date range, or group counts by table.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date YYYY-MM-DD
fromNoStart date YYYY-MM-DD
limitNoMax records (default 50)
tableNoOnly records of this table, e.g. incident
summaryNoReturn counts per table instead of rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by identifying the data source (sys_ai_record_activity) and the shape of each row, but says nothing about log retention, coverage windows, or pagination behavior beyond the limit parameter.

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?

A single dense sentence plus a short capability clause, with the resource identified first and the filtering/grouping options last. No filler and nothing repeated from 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?

There is no output schema, and the description compensates by stating that rows carry table, record, and AI-updated fields. For a read-only list tool with fully described parameters and annotations covering safety, that is nearly complete; only retention/coverage caveats are missing.

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 coverage is 100%, so all five parameters including date formats and the 50-record default are already documented in the schema. The description's 'filter by table and date range, or group counts by table' largely restates the table/from/to/summary semantics rather than adding format or edge-case meaning.

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 (list) and a precisely scoped resource: records changed by AI (Otto / Now Assist, AI agents) drawn from the sys_ai_record_activity log. Naming the underlying table and the returned fields (table, record, which fields AI updated) lets an agent distinguish this from a generic query_records call 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 Guidelines3/5

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

The description says what the tool can do with its parameters ('Filter by table and date range, or group counts by table'), which implies usage but gives no explicit when-to-use vs when-not guidance. It names no alternative sibling for the case where an agent wants general record querying rather than AI-attributed changes.

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

Deploy Server

Other Tools