Skip to main content
Glama

watch_terms

Watch a terms-of-service URL for changes. Establishes a quoted, scored baseline NOW, then every check compares the live document to it: unchanged checks are free, changed documents are re-scanned and diffed, and material changes (score jump, new high/critical clause, worsened verdict) raise an alert, POSTed to webhook_url when set.

Use this when the principal depends on a vendor long-term: the agent
should know when the terms it agreed to change underneath it.

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": {
      "url": "<url>"
    },
    "name": "watch_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
webhook_urlNo
interval_daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full load and does so well: it discloses that a scored baseline is captured at call time, that unchanged checks are cheap ("free") while changed documents are re-scanned and diffed, that only material changes (score jump, new high/critical clause, worsened verdict) alert, and that alerts are POSTed to webhook_url. It omits operational details such as persistence/scheduling lifecycle, permissions, and how to stop watching.

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 description is front-loaded with the verb+resource, then layers baseline behavior, cost model, and alert conditions in a logical order with no filler paragraphs. Phrasing like "quoted, scored baseline NOW" and "change underneath it" is slightly mannered but each sentence still contributes substantive information.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the core watch/alert mechanics are covered. However, for a monitoring tool the description never addresses the monitor lifecycle (how often checks run given interval_days, how to list or stop a watch) and leaves one parameter unexplained, which is a real gap at this complexity level.

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 description coverage is 0%, so the description must supply all parameter meaning. It explains url (the document to watch) and webhook_url (where alerts are POSTed, only when set), but interval_days is never mentioned, leaving one of three parameters with no semantics beyond its self-descriptive name and default of 7.

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 first sentence gives a specific verb and resource ("Watch a terms-of-service URL for changes"), and the rest clarifies that it establishes a baseline then re-checks on a schedule. It implicitly contrasts with one-off scanning (scan_terms_of_service, batch_scan_terms are siblings) but never names any sibling to make the distinction explicit.

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 states a clear triggering condition: use it "when the principal depends on a vendor long-term" and needs to know when agreed terms change. There is no exclusion guidance telling an agent when a single scan or a text scan is the better choice, so the agent must infer the one-off vs. ongoing split.

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.