Skip to main content
Glama
Sign In
OpenUptime

OpenUptime

by becoolme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

run_check

Trigger an immediate monitor check to record results through incident/alert workflows, or use a region for an unrecorded spot check that leaves history and status unchanged.

Instructions

Check a monitor immediately. Without region, records the result through the normal incident/alert workflow and returns {ok:true}; it can notify channels. With region from list_regions, returns {ok:true,region,result} for an unrecorded spot check without changing monitor history/status. Use get_monitor to read existing checks. Heartbeats have no outgoing spot check; hosted check credits apply and probe/network errors are returned.

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": {
      "id": "<id>"
    },
    "name": "run_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource UUID returned by the matching list tool; not its name, incident number or status-page slug.
regionNoAn id returned by list_regions; omit for a normal recorded check, provide for an unrecorded spot check.
projectNoProject id (from list_workspaces). Omit to use the default project of the workspace.
workspaceNoWorkspace id (from list_workspaces). Omit to use the default one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"Resource id (uuid)"New value: +"Resource UUID returned by the matching list tool; not its name, incident number or status-page slug."
    • addedInput schema / properties / region / description
      Added value: +"An id returned by list_regions; omit for a normal recorded check, provide for an unrecorded spot check."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag openWorldHint, non-idempotent, non-destructive, non-readOnly; the description supplies the substance: results go through incident/alert workflow and can notify channels, spot checks change no monitor history/status, hosted check credits apply, and probe/network errors are returned.

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 action and the two modes, dense but nearly every sentence carries a distinct fact. The final sentence bundles three unrelated caveats (heartbeats, credits, errors), which slightly muddies structure.

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?

No output schema exists, and the description compensates by naming both return shapes ({ok:true} vs {ok:true,region,result}), the side effects, and the error behavior. An agent has enough to call it correctly and predict consequences.

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 behavioral meaning to region: omission produces a recorded check, presence produces an unrecorded one with a different return shape. The id/project/workspace params get no extra treatment beyond the schema.

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?

Opens with a specific verb+resource: 'Check a monitor immediately.' It also contrasts with get_monitor ('read existing checks'), so an agent can distinguish it from the sibling read tool without opening either schema.

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?

Explicitly states when to omit region, when to provide it (after list_regions), and directs read-only use to get_monitor. It also excludes a case: 'Heartbeats have no outgoing spot check.'

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

Deploy Server

Other Tools