QuietDiff

create_monitor

Creates a new website monitor with field extraction. JavaScript rendering (renderJs) is available on Starter plan and above, with an hourly minimum.

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": "<name>",
      "checkInterval": "<checkInterval>",
      "fields": "<fields>"
    },
    "name": "create_monitor"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	URL to monitor
`name`	Yes	Monitor name
`fields`	Yes	Fields to extract
`waitFor`	No	For renderJs: "networkidle" or CSS selector to wait for
`renderJs`	No	Enable JavaScript rendering (Starter+, hourly min, plan limits apply)
`checkInterval`	Yes	Check interval in seconds (3600+ for JS monitors)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

B3.4/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 full burden. It usefully discloses plan gating for renderJs (Starter and above, hourly minimum), which is real behavioral context, but it says nothing about whether the monitor starts running immediately, whether creation consumes credits or quota, how many fields are permitted, or what happens when the URL or selectors fail validation. For a no-annotation mutation tool these are meaningful omissions.

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 sentences, front-loaded with the core action and with no filler. The second sentence is somewhat redundant with the schema's own renderJs and checkInterval descriptions, which slightly reduces its value but does not make it bloated.

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?

This is a six-parameter, four-required creation tool with no annotations and no output schema, so the description is the only place an agent can learn about post-creation behavior. It covers the plan constraint but leaves out return shape (e.g. the created monitor's id), immediate-scheduling behavior, and any limits on the nested fields array, which is short of what a no-annotation write tool warrants.

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 100%, so every one of the six parameters is already documented in the schema, which sets the baseline at 3. The description's statement about renderJs and the hourly minimum largely restates the schema text for renderJs and checkInterval rather than adding syntax, defaults, or inter-parameter constraints beyond it.

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 gives a specific verb and resource ('Creates a new website monitor') plus the qualifying detail 'with field extraction', which tells an agent what kind of monitor is produced. It does not name or distinguish itself from the sibling create_from_template, so an agent must infer the difference from the names alone.

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 implied by the name and by the 'web'

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

All QuietDiff tools Inspect

Try in Browser