Skip to main content
Glama

Get a Network change

get_network_update

Retrieve a specific website change by ID, including before/after values, detection time, summary, and evidence URLs for verification.

Instructions

One change with its evidence: before/after values, summary, when Monity detected it, and the evidence files (screenshots of before and after, the visual diff) as URLs. Evidence is Monity's own copy, captured when it checked the page.

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": {
      "id": "<id>"
    },
    "name": "get_network_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe change id (publicId from get_network_changes or get_network_watch)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does add useful behavioral context that structured fields lack: the evidence is Monity's own archived copy captured at check time, and what fields accompany the change. It does not state that the call is read-only, what happens with an unknown or stale id, or whether evidence can be missing.

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?

Two tight sentences, front-loaded with the result shape and followed by a single clarifying note about evidence provenance. No filler; the phrasing "when Monity detected it" is slightly awkward but still readable.

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?

With no output schema, the description must explain the return value, and it does so concretely (values, summary, timestamp, evidence URLs). What remains unstated—error behavior for an invalid id and whether evidence is always present—is minor for a one-parameter read tool.

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?

One parameter with 100% schema description coverage, so the schema already explains that `id` is the change publicId. The description adds nothing about the identifier, so baseline 3 applies.

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?

"One change with its evidence" establishes a single-record retrieval and enumerates the payload (before/after values, summary, detection time, evidence URLs). That implicitly contrasts with the plural listing siblings, but the description never names a sibling or states the retrieval verb explicitly enough to fully separate it from get_network_changes or summarize_network_changes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer that this is the detail-fetch step after get_network_changes; only the schema (not the description) mentions where the id comes from.

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