Skip to main content
Glama

get_check_results

Read-onlyIdempotent

Check results. view is status, history, or outages; server checks also take servers and metrics. history uses hours (default 24) and returns status, status_code, latency_ms, ttfb_ms (time to first byte), dns_ms, connect_ms, location_name, location_region, and observed_at. Sample metadata is omitted. servers returns each machine (state active, left, or lost; last_seen; agent_version and outdated; the latest cpu, mem, disks, net, and procs) and the alert rules with alert_open and alert_detail (which servers breach). metrics uses hours (1, 6, 24, 48, 168, or 720; default 24; Free keeps 7 days) and returns points with cpu, mem, disk, load, and network averages and maxima across the fleet.

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": {
      "endpoint_id": "<endpoint_id>",
      "view": "<view>"
    },
    "name": "get_check_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
hoursNo
endpoint_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses real behavioral traits: sample metadata is omitted from history, Free plans retain only 7 days of metrics, and hours defaults to 24. It does not discuss pagination, empty-result behavior, or error conditions when a non-server check is queried with servers/metrics.

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?

The text is dense and front-loaded by view, with each sentence contributing view-specific parameters and return fields rather than filler. Some parenthetical enumerations (return field lists) are heavy, but they substitute for absent schema documentation, so they largely earn their place.

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 3-parameter read tool with an output schema, the definition covers view selection, hours semantics, plan limits, and per-view return shapes, so an agent can call it correctly. The remaining gap is endpoint_id semantics and failure behavior for invalid view/check combinations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the full burden and does so well: it enumerates the valid view values, ties servers/metrics to server checks, and specifies the allowed hours set (1, 6, 24, 48, 168, 720) with a default. Only endpoint_id is left unexplained, which is minor given the tool's naming.

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?

"Check results" is a noun phrase rather than a verb+resource, but the following sentences make it clear this returns result data for a check across several views (status, history, outages, servers, metrics). It is distinguishable from get_check (configuration) by implication, though it never states the distinction or names a sibling explicitly.

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?

The description effectively tells an agent which view to pick and under what constraint: "server checks also take servers and metrics", implying non-server checks do not. It gives concrete context for history, servers, and metrics, but offers no explicit when-not guidance or routing away from get_check.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources