Skip to main content
Glama
Sign In
SolidPing

SolidPing

Official
by fclairamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Run check now

run_check

Trigger an immediate uptime check across all regions instead of waiting for the next scheduled run—use it after a fix or for a new check, with results following the normal incident path.

Instructions

Run a check once, now, in every region, instead of waiting for its next period (use it right after a fix, or on a freshly created check). The run goes through the normal result path: it can open or resolve an incident like any scheduled run. Rate limited per check and per organization. A region status of queued means due now, or right after the run in progress; read the outcome with diagnose_check or list_results (a result with periodStart >= requestedAt). Requires the mcp scope (mcp:read tokens are refused) and at least the user role in the organization.

Input Schema

NameRequiredDescriptionDefault
identifierYesCheck UID or URL-friendly slug, e.g. "api-prod" or "63d49e55-97e3-4e8c-b7ab-c862de7a43f3".

Output Schema

NameRequiredDescriptionDefault
regionsYesOne entry per region.
requestedAtYesRFC3339 time the request was recorded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.42.0
    • addedInput schema / properties / identifier / maxLength
      Added value: +2048
    • addedInput schema / properties / identifier / minLength
      Added value: +1
  2. Changed2 schema fields changedv0.41.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedOutput schema / additionalProperties
      Added value: +false
  3. Addedv0.38.5

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, but the description adds context the annotations cannot: rate limits per check and per organization, that the run goes through the normal result path and can open or resolve an incident, the queued region-status semantics, and the exact auth requirements (mcp scope; mcp:read tokens refused; user role required). This is rich behavioral disclosure consistent with the annotations.

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?

It is front-loaded with the core action and flows logically into side effects, rate limits, outcome reading, and auth. It is dense with several parentheticals, but each sentence carries distinct, non-redundant information; slightly more compression would earn 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?

For a mutation-like trigger tool with an output schema, the description supplies everything an agent needs beyond the structured fields: when to call it, side effects on incidents, rate-limit behavior, region status semantics, where to read the result, and permission prerequisites.

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% and the single identifier parameter is fully documented in the schema (UID or slug, examples, length bounds). The description adds no parameter-level syntax or constraints beyond what is already structured, so the baseline 3 applies.

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?

A specific verb and resource with exact scope: run a check once, now, in every region, contrasted with waiting for its next period. An agent can distinguish this from sibling tools like get_check or list_results without opening any 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?

It states when to use it (right after a fix, or on a freshly created check) and names the alternatives for reading the outcome (diagnose_check or list_results, with the periodStart >= requestedAt discriminator). Nothing is left to inference about choosing this tool over a scheduled run or a read tool.

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