Skip to main content
Glama

Website changes of a monitor

get_website_changes
Read-only

For a website or API monitor: its security headers grade with what each missing or weak header does and how to fix it, its DNS records (A, AAAA, CNAME, NS, MX, SPF, DMARC) and the networks its addresses belong to, its page fingerprint (Business: title, external script hosts, and the latest change waiting to be accepted) and the recent header and DNS changes. Settings are header_watch, dns_watch, dns_address_changes, content_watch and content_threshold on update_monitor. Free.

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

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context: the exact payload shape, that a pending page change is surfaced ('waiting to be accepted'), and that the call is 'Free' (no credit cost). It says nothing about what happens when the relevant watchers are disabled or how much history is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense run-on sentence packing four different result categories plus a trailing settings sentence and a pricing note. It is front-loaded with the scope ('For a website or API monitor'), which is good, but the enumerated clauses are hard to scan and the settings sentence belongs more to update_monitor than to this read tool.

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 carries the burden of describing return values, and it does so with reasonable specificity across headers, DNS record types, network ownership, fingerprint, and change history. Gaps remain around behavior when watchers are off and the depth/history of 'recent changes', but for a read-only single-parameter tool this is close to sufficient.

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% and the sole parameter is documented in the schema as the UUID from list_monitors, so the baseline of 3 applies. The description adds no meaning about the id parameter beyond the schema, though none is really needed for a single required key.

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 names a specific resource and enumerates its parts: security headers grade, DNS records, page fingerprint, and recent header/DNS changes for a monitor. An agent can distinguish this from get_monitor (settings) or check_website (on-demand run) because it reads as a stored-data retrieval tool. It stops short of a crisp one-line 'returns the watch results for a monitor' framing, since the content is presented as a long list.

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?

Usage is only implied: the reader must infer this is the tool for inspecting header/DNS/content watch output. The pointer to 'header_watch, dns_watch, dns_address_changes, content_watch and content_threshold on update_monitor' tells the agent where to enable the features but never states when to call this tool versus get_monitor or get_monitor_results. No exclusions or prerequisites are given.

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.

Resources