Skip to main content
Glama

Query Network change records

query_network_records

Retrieve structured change records for a page, site, or tracker, filtered by date, change type, or origin, to review exact history and evidence.

Instructions

Structured change records (schema monity.network.change/1) for one page, one site or one tracker, newest first: page id, what changed (kind, before, after, summary), whether Monity detected it, the tracker's owner posted it or an external source posted it, when, and evidence links. A page can be given as any form of its address (www., tracking parameters and a trailing slash do not matter) or as its page id (pg_…), and every form finds the same records. Use for exact, filterable history (a date range, only price changes, only detected changes); get_network_changes is the simpler feed.

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": "query_network_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
pageNoA page address or page id
siteNoEvery page on a site, e.g. nike.com
limitNo
sinceNoFrom this ISO 8601 date or time
untilNoBefore this ISO 8601 date or time
watchNoA one-source tracker's slug or id
cursorNonextCursor from the previous page
originNoDETECTED: Monity saw it, with evidence. HUNTER: posted by hand by the tracker's owner

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the record schema id, result ordering ('newest first'), per-entity scoping, and that every address form resolves to the same records. It does not mention permissions, rate limits, or the default page size when limit is omitted, which keeps it short of a 5 for an unannotated read tool.

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?

Scope and ordering come first, then record contents, then address handling, then the sibling comparison — a sensible front-loaded order with no filler. The second sentence is long and clause-heavy, which costs a point on readability but not on content value.

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 naming the fields returned and their order, plus cursor pagination is covered by the schema. For a 9-parameter, all-optional filtering tool it is nearly complete; only default limit behavior and whether unfiltered calls return all records are left unstated.

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?

Beyond the 78% schema coverage, the description adds real meaning: page accepts 'any form of its address (www., tracking parameters and a trailing slash do not matter) or as its page id (pg_…)' and all forms find identical records; kind, since/until, origin and watch are each tied to a concrete use case. This normalization guarantee is not expressible in the schema and is exactly the kind of guidance that prevents wrong calls.

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 opens with a specific verb+resource and scope: 'Structured change records (schema monity.network.change/1) for one page, one site or one tracker, newest first,' then enumerates the returned fields (kind, before, after, summary, detection, origin, timing, evidence links). An agent can distinguish it from get_network_changes and the watch-management siblings without opening any 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?

It states the selecting condition explicitly — 'Use for exact, filterable history (a date range, only price changes, only detected changes)' — and routes the agent to the simpler alternative: 'get_network_changes is the simpler feed.' This is the when-to-use vs. alternative pattern done properly.

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