Skip to main content
Glama

Get Network changes

get_network_changes

Retrieve what changed on the public Monity Network for a whole site or a single tracker, optionally only since a date. Returns each change's title, before/after values, AI summary, source and citation URL.

Instructions

What changed on the public Monity Network, newest first: on a whole site ("what changed on nike.com this week") or on one tracker, optionally only since a date. Each change has its title, before/after values, an AI summary when there is one, who it came from (Monity detected it, with evidence; the tracker's owner posted it; or an external source posted it), and a url to cite. Give exactly one of domain, watchlist (a tracker with several sources) or watch (a tracker with one source).

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 20)
sinceNoOnly changes from this ISO 8601 date or time on, e.g. 2026-09-01
watchNoA one-source tracker's slug or id
cursorNonextCursor from the previous page
domainNoA site, e.g. nike.com or https://www.nike.com/…
watchlistNoA tracker's slug or id, for a tracker with several sources

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/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 disclosure burden and does real work: it states result ordering (newest first), what each change record contains (title, before/after values, AI summary, provenance of the change, citation url), and that the data is public. It omits pagination behavior and any auth or rate-limit caveats, which keeps it from a 5.

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?

The scope and ordering are front-loaded in the first clause, and the selector rule cleanly closes the description. The parenthetical breakdown of provenance types (Monity detected with evidence, owner posted, external source posted) is comparatively verbose for its value, but the passage is otherwise dense and waste-free.

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 six-parameter, no-required, no-output-schema, no-annotation read tool, the description supplies the return shape and the selection rule an agent needs. The remaining gap is pagination: cursor and limit exist in the schema but the description never explains paging through results or the default page size.

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%, so the baseline is 3, but the description adds the schema-absent rule that exactly one of domain, watchlist, or watch must be supplied — critical since the schema marks nothing required and has no oneOf constraint. It also glosses watchlist as a multi-source tracker and watch as a one-source tracker, though that gloss largely restates the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource framing ("what changed on the public Monity Network, newest first") and defines the two scope levels: a whole site or a single tracker. The "exactly one of domain, watchlist or watch" constraint further sharpens its identity. It does not, however, distinguish itself from plausible siblings such as get_recent_changes or query_network_records, so it stops short of a 5.

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 provides concrete use-case framing through quoted example questions ("what changed on nike.com this week") and states the optional since-date narrowing. The selector constraint tells the agent how to phrase a valid call. There is no explicit when-not guidance and no named alternative tool for the agent to route to instead.

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