Ground Truth - Fresh Evidence for AI Agents

Create Monitor

create_monitor

Create a persistent monitor that tracks a URL, pricing page, package version, endpoint status, vendor claim, or custom keyword pattern over time. Monitors run automatically on their configured schedule (hourly/daily/weekly) via the Cloudflare cron trigger, or on demand with run_monitor_now. Results are stored durably by account. A free watch key includes three daily or weekly monitors; paid plans add hourly schedules and higher limits.

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": {
      "name": "<name>",
      "target_type": "<target_type>",
      "target_value": "<target_value>"
    },
    "name": "create_monitor"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Human-readable name for this monitor.
`schedule`	No	How often the monitor runs automatically. manual means only via run_monitor_now.	daily
`target_type`	Yes	What to monitor. url/endpoint: HTTP reachability and status. pricing_page: pricing signals (prices, plans, free tier). package: package version on npm or pypi (target_value as 'npm:pkg-name' or 'pypi:pkg-name'). vendor_claim: keyword presence at a URL (target_value=claim text, instructions=URL to check). custom_prompt: comma-separated keywords checked against a URL (target_value=URL, instructions=keywords).
`instructions`	No	Supplementary instructions. For vendor_claim: the URL to check. For custom_prompt: comma-separated keywords. Optional for other types.
`target_value`	Yes	Primary target. For url/endpoint/pricing_page/custom_prompt: a public https URL. For package: 'npm:package-name' or 'pypi:package-name'. For vendor_claim: the claim text to search for.
`notification_destination`	No	Optional change-alert destination, sent only when a scheduled check detects a change. One of: an HTTPS webhook URL (JSON POST, no API key included), a Slack Incoming Webhook URL (https://hooks.slack.com/...), or an email address as mailto:you@example.com.

Output Schema

Name	Required	Description
`id`	Yes	Unique monitor ID.
`name`	Yes	Monitor name.
`error`	No	Error message if creation failed.
`schedule`	Yes	Monitor schedule.
`created_at`	Yes	Creation timestamp ISO 8601.
`target_type`	Yes	Monitor target type.
`target_value`	Yes	Monitor target value.
`active_monitor_limit`	No	Maximum active monitors included in the current plan.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / notification_destination / description

Previous value: -"Optional HTTPS webhook URL. A POST is sent only when a scheduled check detects a change; no API key is included."New value: +"Optional change-alert destination, sent only when a scheduled check detects a change. One of: an HTTPS webhook URL (JSON POST, no API key included), a Slack Incoming Webhook URL (https://hooks.slack.com/...), or an email address as mailto:you@example.com."

Changed1 schema field changedAug 27, 2026

changedOutput schema / properties / active_monitor_limit / description

Previous value: -"Maximum active monitors included in the paid plan."New value: +"Maximum active monitors included in the current plan."

Changed2 schema fields changedAug 7, 2026

changedInput schema / properties / notification_destination / description

Previous value: -"Optional destination reserved for a future alert-delivery integration."New value: +"Optional HTTPS webhook URL. A POST is sent only when a scheduled check detects a change; no API key is included."

addedOutput schema / properties / active_monitor_limit

Added value: +{
+  "description": "Maximum active monitors included in the paid plan.",
+  "type": "number"
+}

Changed1 schema field changedJul 17, 2026

changedInput schema / properties / notification_destination / description

Previous value: -"Optional destination for change alerts (email or webhook URL). Stored for future use."New value: +"Optional destination reserved for a future alert-delivery integration."

AddedMay 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world mutation. The description adds real context beyond that: execution runs on a Cloudflare cron trigger, results are stored durably per account, and quota tiers govern allowed schedules. It omits what happens if a monitor with the same name already exists and whether duplicates are created — notable given idempotentHint=false.

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?

Four sentences, front-loaded with the core action and supporting detail afterward; the quota sentence earns its place by setting expectations. The target-type enumeration slightly duplicates the schema enum, which keeps it from a 5.

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

Completeness5/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 description covers scheduling behavior, storage durability, quota limits, and the on-demand alternative. Nothing an agent needs to invoke this correctly against six parameters is missing.

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 the parameter meanings, enums, and per-target-type conventions are already fully documented in structured fields. The description restates the target-type list in prose but adds no syntax, format, or constraint detail the schema does not already carry. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a persistent monitor') and enumerates the exact target types it tracks (URL, pricing page, package version, endpoint status, vendor claim, keyword pattern). The word 'persistent' plus the scheduling sentence implicitly separates it from preview_monitor and run_monitor_now, so an agent can distinguish it from siblings without opening a schema.

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?

Explicitly routes on-demand execution to run_monitor_now and explains that 'manual' scheduling exists only via that path, plus lays out the free-versus-paid schedule limits. It stops short of saying when to prefer check_endpoint, check_pricing, or preview_monitor over creating a persistent monitor, so the exclusion set is incomplete.

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

All Ground Truth - Fresh Evidence for AI Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Create Monitor

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources