Skip to main content
Glama

api_change_check__watch

Stateful monitor callable with plain query params: GET /s/api-change-check/watch?token=my-api-prod&url=https://example.com/openapi.json . Fetches your public OpenAPI 3 JSON; first call stores a baseline, later calls return only what changed. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/api-change-check/watch

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of your OpenAPI 3.0/3.1 JSON document
tokenYesPrivate label for this monitored API, 8-64 chars of letters/digits/-/_

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses statefulness, baseline creation, diff-only returns on later calls, the $0.01 USDC price on Base (eip155:8453), and the x402 payment channel in params._meta['x402/payment']. What it omits is baseline lifecycle details (overwrite, expiry) and error behavior when the URL is unreachable, but the payment and state model are unusually well covered.

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?

The key facts are front-loaded, but the HTTP endpoint is stated twice (in the query-param example and again at the end), which is redundant. The payment sentence is dense but earns its place; the duplication and the inline URL clutter reduce efficiency.

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 two-parameter tool with no annotations and no output schema, the description covers cost, payment mechanics, statefulness, and return semantics (only what changed). The chief remaining gap is a sketch of what the diff response contains, since no output schema exists to describe it.

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%, so the schema already documents both parameters in detail, giving a baseline of 3. The description adds illustrative example values (token=my-api-prod, url=https://example.com/openapi.json) that hint at usage patterns, but nothing about token uniqueness constraints or URL validation beyond what the schema states.

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 states a specific verb and resource: it fetches a public OpenAPI 3 JSON document and monitors it for change. It also discloses the stateful baseline-then-diff behavior, which makes it separable from a plain fetch tool. It does not explicitly contrast itself with siblings like api_change_check__compare or api_change_check__monitor, so it is clear but lacks sibling differentiation.

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?

The line 'first call stores a baseline, later calls return only what changed' implies the repeat-call usage pattern, which is useful context. However, there is no explicit statement of when to pick this over the sibling compare or monitor tools, nor any exclusion or precondition guidance beyond the implied requirement for a public URL.

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