Skip to main content
Glama

Run a check now

run_monitor

Trigger an immediate check of an active monitor's page instead of waiting for its schedule; results appear via get_latest_result. Resume paused monitors first.

Instructions

Check an active monitor's page now instead of waiting for its schedule (requires a write-scope API key). The check runs in monity.ai's cloud browser and takes up to a minute or two; then get_latest_result shows it. Counts against the plan like any check. Resume a paused monitor first.

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": {
      "uuid": "<uuid>"
    },
    "name": "run_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.5/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 it well: it discloses the write-scope API key requirement, the cloud-browser execution model, latency of up to a minute or two, plan quota consumption, and the state prerequisite. It stops short of stating error behavior (e.g., what happens if the monitor is paused or a check is already in flight) or whether the call returns anything immediately.

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?

The action and its timing contrast are front-loaded, then operational facts (auth scope, latency, result retrieval, quota, prerequisite) follow in short clauses. No sentence is filler and each carries distinct information.

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?

For a single-parameter trigger tool with no output schema, everything an agent needs to call it correctly is present: cost, latency, auth scope, prerequisite state, and where the result appears. Nothing material is missing given the tool's simplicity.

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% with a single required uuid already documented as coming from list_monitors, so the schema does the heavy lifting. The description only adds the implicit constraint that the monitor must be active, not the uuid format or sourcing details. Baseline 3 is appropriate.

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 ('Check an active monitor's page now') and immediately contrasts it with the scheduled behavior it bypasses. The follow-up pointer to get_latest_result makes it distinguishable from the sibling that reads results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the condition that selects this tool ('instead of waiting for its schedule'), the prerequisite state ('Resume a paused monitor first'), and the alternative retrieval path (get_latest_result). An agent can decide between this and waiting without further inference.

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