Skip to main content
Glama

Check results

get_monitor_results
Read-only

A monitor's most recent check results, newest first. Older results may be merged: repeats checks with the same outcome up to last_checked_at. Free.

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": "get_monitor_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.
limitNoHow many results to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many results to return."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are ordered newest-first, repeated checks with the same outcome may be merged up to last_checked_at, and the call is free — the merging caveat is critical for correct interpretation of counts.

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?

Three short, front-loaded sentences with no padding; the freshness/ordering claim comes first and the merging caveat follows. Minor phrasing awkwardness ('repeats checks') and the terse one-word 'Free.' sentence cost it little but keep it from a 5.

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

Completeness3/5

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

There is no output schema, so the description should hint at the shape of a check result; it explains ordering and merging but not what fields each result carries. For a simple two-parameter read tool this is adequate, but the return payload remains opaque.

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%, documenting both id (with its source, list_monitors) and limit (default 50, max 500). The description adds no additional meaning about the limit or ID semantics, so the baseline 3 applies.

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?

The description names a specific resource (a monitor's most recent check results) and its ordering (newest first), which distinguishes it from config-level siblings like get_monitor and aggregate ones like get_uptime_history. It stops short of naming any alternative explicitly, but an agent can tell what it returns.

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

Usage Guidelines3/5

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

Usage is only implied: use it when you want raw recent check results for one monitor whose ID came from list_monitors. There is no explicit statement of when to prefer this over get_uptime_history or get_incident, and no exclusions or prerequisites (e.g. auth/plan) are given.

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