All's Well

Create Monitor Tool

create-monitor

Create an uptime monitor for the team. Call get-plan-usage first to confirm there is room and to find the shortest allowed interval. A heartbeat monitor returns the heartbeat_url your job must request after each run.

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>",
      "type": "<type>",
      "check_interval_minutes": "<check_interval_minutes>"
    },
    "name": "create-monitor"
  }
}

Input Schema

Name	Required	Description
`url`	No	A full URL such as https://shop.example.com. tcp and icmp use only its host. Required unless type is heartbeat.
`name`	Yes	Human-readable monitor name.
`port`	No	Required when type is tcp: port 1-65535.
`type`	Yes	Monitor type. http, ssl, keyword, tcp and icmp need a url; tcp also needs a port; heartbeat waits for your job to ping it. The type cannot change later.
`password`	No	HTTP basic-auth password. Stored encrypted and never returned.
`username`	No	HTTP basic-auth user name.
`is_active`	No	false creates the monitor paused (default true).
`http_method`	No	HTTP method (default GET).
`request_headers`	No	Extra request headers, name to value, e.g. {"X-Env": "live"}.
`expected_keyword`	No	Required when type is keyword: text expected in the response body.
`expected_status_codes`	No	HTTP status codes counted as up (default [200]).
`check_interval_minutes`	Yes	Check frequency in minutes. Must be allowed by the plan (free = 5 or more).
`check_interval_seconds`	No	Optional exact interval in seconds, at least the plan minimum; overrides the minutes. For a daily heartbeat use about 90000.
`request_timeout_seconds`	No	Request timeout 1-60 seconds (default 30).
`ssl_expiry_warning_days`	No	Warn this many days before SSL expiry (default 14).
`notification_contact_ids`	No	IDs from list-notification-contacts to alert when this monitor changes state.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations contain only a title, so the description carries the full burden. It usefully discloses the plan-capacity dependency and that heartbeat monitors return a heartbeat_url the job must request after each run, but it says nothing about permissions, whether monitors start active by default (schema covers that via is_active), or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action, then prerequisite, then the one non-obvious return behavior. No filler.

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 16-parameter creation tool with no output schema, the description covers the plan prerequisite and the heartbeat return value but leaves out what the call returns in general and any warning that creating a monitor begins alerting notification contacts. Adequate but with clear gaps.

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 schema already documents all 16 parameters in detail. The description adds only the framing that the interval chosen must fit the plan's minimum, which is a mild supplement rather than new parameter semantics.

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?

States a specific verb and resource ('Create an uptime monitor for the team') and hints at type-specific behavior (heartbeat monitors return a heartbeat_url). It does not explicitly differentiate from update-monitor, but 'create' versus 'update' is implicit in the names.

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 tells the agent to call get-plan-usage first to verify capacity and discover the shortest allowed interval, which is concrete prerequisite sequencing. It stops short of naming when not to use this tool or when update-monitor would be the better choice.

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

All All's Well 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.

Resources

Need Help?