Skip to main content
Glama

Read a monitor's records

get_monitor_rows
Read-onlyIdempotent

Read the records an agent monitor follows -- one per item its answer lists, e.g. each plan of a pricing page -- as they stand, with the page each value was read on; and, with changes=true, what moved: records added, a column changed (before and after), records gone. Use it for a monitor made with follow_rows=true, to answer what changed or what the list is now. list_monitors shows a run's summary; this is the record-level detail. Inputs: monitor_id from list_monitors. active=false lists the records gone instead. q keeps records holding it. limit is 1 to 500 (100 by default). Read-only and free: it reads stored data and never fetches.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "get_monitor_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeep records holding this text.
limitNoThe most records to return, 1 to 500.
activeNotrue (default) lists the records as they stand; false the records gone.
changesNotrue also returns what moved, newest first, at most 50.
monitor_idYesThe monitor's id, from list_monitors or create_monitor.

Output Schema

NameRequiredDescriptionDefault
codeNoOnly on a failure: a machine-readable reason, e.g. read_only, validation, plan_limit or not_found.
noteNoWhat was left out and how to get it.
rowsNoThe records as they stand, each {key, attrs (its columns), sources (the page each was read on), url, active, withheld, firstSeen, lastSeen}, at most `limit`.
errorNoOnly when the call failed: what went wrong, in words an assistant can act on.
totalNoHow many records match, whatever `limit` returned.
detailNoOnly on a failure: the API's own wording, when the error was rephrased.
eventsNoWith changes=true: what moved, newest first -- records added, a column changed (before and after), records gone or withheld -- at most 50.
statusNoOnly on a failure: the HTTP status code.
monitor_idNoThe monitor read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive read behavior, but the description adds real value: it discloses that changes=true returns additions, before/after column changes, and removals, capped at 50 newest-first, and that the tool reads stored data and 'never fetches' (cost/latency context). Minor redundancy with readOnlyHint in the closing 'Read-only and free' line, but the delta semantics justify a 4.

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?

Purpose and routing are front-loaded, and every sentence (variant behavior, sibling contrast, input summary, cost) carries information. The opening sentence is long and dash-heavy with an embedded example, which makes it slightly harder to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema already exists, the description needn't spell out return shapes, and it still sketches the change payload sufficiently. With all five parameters bounded and cost/read semantics stated, an agent has everything needed to call this correctly.

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 the schema already documents q, limit, active, changes, and monitor_id; the description mostly restates those bounds (1 to 500, 100 default) and the source of monitor_id. It adds only marginal meaning, so the baseline 3 applies.

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 (read a monitor's records) plus the exact unit of a record ('one per item its answer lists, e.g. each plan of a pricing page'). It also distinguishes the mode where changes=true returns deltas, so an agent can tell what it gets without opening the 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?

Explicitly scopes use to 'a monitor made with follow_rows=true' and names the alternative: 'list_monitors shows a run's summary; this is the record-level detail.' It also routes the variant case ('active=false lists the records gone instead'), leaving little to inference.

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.