Skip to main content
Glama
fclairamb

SolidPing

Official
by fclairamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

list_results

Query uptime monitoring results with filters for check, type, status, region, and time range to analyze trends or inspect specific windows.

Instructions

Query monitoring results (raw or aggregated) with filtering by check, type, status, region, period type, and time range. Use this for trend analysis or to inspect a specific window. For investigating a single check's current state, use diagnose_check instead. Defaults: if periodType is omitted it falls back to "hour". If periodStartAfter is omitted it falls back to a window matched to the finest periodType requested (raw=1h, hour=24h, day=30d, month=365d). The response includes effectiveFilter so you can see exactly what filter actually ran.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoMax results (1-100, default 20).
withNoComma-separated extra fields: durationMs — response time in ms durationMinMs — min response time in the bucket (aggregated rows only) durationMaxMs — max response time in the bucket (aggregated rows only) region — region the check ran in metrics — per-execution metrics output — full check output incl. error messages availabilityPct — uptime % (aggregated rows only) checkSlug — slug of the check checkName — human name of the check Example: "durationMs,output".
cursorNoOpaque pagination cursor returned by a previous response. Omit on the first page.
regionNoComma-separated region slugs, e.g. "eu-west-1,us-east-1".
statusNoComma-separated result statuses. Allowed: up, down, created, running, abandoned. "down" covers every genuine failure (down, timeout, error); "abandoned" is separate on purpose — it marks an attempt nothing was ever reported for, which is excluded from availability and is NOT downtime. Example: "down" or "down,abandoned".
checkUidNoComma-separated check UIDs or slugs to filter by, e.g. "api-prod,db-prod".
checkTypeNoComma-separated check types. Allowed: http, tcp, icmp, dns, ssl, heartbeat, domain. Example: "http,dns".
periodTypeNoComma-separated period types. Allowed: raw (single executions), hour, day, month (rollups). Defaults to "hour" when omitted. Example: "raw".
periodEndBeforeNoRFC3339 timestamp (exclusive upper bound), e.g. "2026-05-03T11:00:00Z".
periodStartAfterNoRFC3339 timestamp (inclusive lower bound), e.g. "2026-05-03T10:14:22Z". Defaults to a window matched to periodType when omitted (raw=1h, hour=24h, day=30d, month=365d).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.32.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the read-only query intent, the raw vs aggregated distinction, default fallback behavior for periodType and periodStartAfter, and the effectiveFilter transparency mechanism. It does not cover return shape or pagination behavior, but the disclosed defaults are meaningful behavioral context.

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 description is compact and front-loaded: the main purpose comes first, then the alternative routing, then the default behavior and transparency guarantee. Every sentence earns its place without repeating the full schema content.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 10-parameter tool with no annotations and no output schema, the description covers scope, filters, aggregation modes, defaults, and filter transparency. It does not describe the default response fields or pagination flow explicitly, but the schema's parameter documentation carries most of the invocation burden.

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 baseline is 3. The description adds the 'finest periodType requested' clarification and the effectiveFilter note, but the parameter meanings and defaults are already thoroughly documented in the schema. The description does not substantially enrich parameter semantics 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?

The description states a specific action and resource: 'Query monitoring results (raw or aggregated) with filtering by check, type, status, region, period type, and time range.' It also explicitly differentiates itself from diagnose_check, so an agent can distinguish it from sibling tools like list_checks, get_check, and diagnose_check.

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 gives explicit usage context: 'Use this for trend analysis or to inspect a specific window' and names the alternative for a different case: 'For investigating a single check's current state, use diagnose_check instead.' This is clear routing guidance with no inference required.

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