Skip to main content
Glama

Get check history

get_check_history

Lists a monitor’s past checks newest first with timestamps, status, alerts, percent difference, errors, and page-access flags to distinguish real changes from challenge, login, or error pages.

Instructions

List a monitor's past checks (newest first): timestamps, status, alerted flag, percent difference, errors. Use get_check for the full detail of one check. pageAccess says what the browser reached; when reachedContent is false the check saw a challenge, login or error page, so report that, not a change in content.

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": {
      "uuid": "<uuid>"
    },
    "name": "get_check_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO date upper bound (inclusive)
fromNoISO date lower bound (inclusive)
pageNoPage number (default 1)
uuidYesMonitor uuid (from list_monitors)
limitNoResults per page (default 10 here, max 100)
statusNoFilter by status: ALERT_SENT, CHANGE, NO_CHANGE, or ERROR
includeHiddenNoInclude changes the user hid (hide_change). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses result ordering and, critically, explains how to interpret pageAccess/reachedContent so the agent reports a challenge, login, or error page rather than a false content change. It omits any note on auth requirements, rate limits, or pagination behavior beyond what the schema states.

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-loads the core purpose and returned fields, then adds the sibling pointer and the interpretation caveat. Three sentences with little waste, though the pageAccess sentence is dense and could be split or tightened.

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?

There is no output schema, and the description compensates by enumerating the returned fields (timestamps, status, alerted flag, percent difference, errors) and warning about misleading page-level results. That is close to complete for a list tool; only pagination and filtering nuance are left entirely to the schema.

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 all seven parameters (from/to/page/limit/status/includeHidden/uuid) are already documented in structured data. The description adds no additional meaning about filtering semantics or pagination, 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?

States a specific verb and resource ("List a monitor's past checks") plus ordering (newest first) and the fields returned. It also explicitly distinguishes itself from get_check, which handles the full detail of a single check, so an agent can choose between the two without opening a schema.

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?

Explicitly routes the agent to get_check for single-check detail, which is clear alternative guidance. It lacks exclusion conditions relative to other lookalike siblings such as get_latest_result or get_recent_changes, so guidance is strong but not exhaustive.

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