Skip to main content
Glama

api_change_check__monitor

Stateful monitor: POST {"token":"...","spec":{...}}; first call stores a baseline, later calls return only what changed since your previous call. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: POST https://api.firstmention.uk/s/api-change-check/monitor

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>",
      "spec": "<spec>"
    },
    "name": "api_change_check__monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYesYour current OpenAPI 3 document as JSON
tokenYesPrivate label for this monitored API, 8-64 chars of letters/digits/-/_

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / spec / description
      Added value: +"Your current OpenAPI 3 document as JSON"
    • removedInput schema / properties / spec / properties
      Removed value: -{
      -  "openapi": {
      -    "type": "string"
      -  },
      -  "paths": {
      -    "properties": {
      -      "/a": {
      -        "properties": {
      -          "get": {
      -            "properties": {
      -              "responses": {
      -                "properties": {
      -                  "200": {
      -                    "properties": {},
      -                    "type": "object"
      -                  }
      -                },
      -                "type": "object"
      -              }
      -            },
      -            "type": "object"
      -          }
      -        },
      -        "type": "object"
      -      }
      -    },
      -    "type": "object"
      -  }
      -}
    • addedInput schema / properties / token / description
      Added value: +"Private label for this monitored API, 8-64 chars of letters/digits/-/_"
    • addedInput schema / required
      Added value: +[
      +  "token",
      +  "spec"
      +]
  2. Added

TDQS

A3.7/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 burden and does substantial work: it discloses persistent baseline state keyed across calls, a per-call price of $0.01 in USDC on Base (eip155:8453), and the x402 payment location in params._meta['x402/payment']. It omits what happens when payment is absent/insufficient and any rate limits, but the payment and statefulness disclosures are the traits an agent most needs.

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?

Front-loaded with the key property ('Stateful monitor') and packed with no filler. The semicolon-chained body, raw endpoint, and pricing details make it dense rather than elegant, but every clause carries operational 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?

For a stateful, paid tool with a nested spec object and no output schema, the description explains the diff-based return at a conceptual level but not its shape, and gives no failure behavior for unpaid or rejected requests. It is callable as written, but the agent cannot anticipate the response structure or error path.

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 baseline is 3, but the description adds meaning beyond the schema: it shows the exact POST body shape and reveals that 'token' is the key that ties calls together into one monitored state ('since your previous call'), whereas the schema only calls it a 'private label'. That state-key implication is not derivable from the schema alone.

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?

Names a specific verb and resource ('Stateful monitor' of an OpenAPI spec) and states the core output ('only what changed since your previous call'). It stops short of explicitly contrasting itself with the stateless-looking siblings like api_change_check__compare, but the stateful framing is distinctive enough to select on.

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 first-call/later-call sequencing implicitly tells the agent how to use it (call once to seed, call again to poll), which is real guidance. There is no explicit statement of when to prefer this over a one-shot comparison or a watch tool, and no guidance on token reuse or polling frequency.

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