Skip to main content
Glama

Get check detail

get_check

Retrieve a specific monitor check by ID with before/after screenshots, highlighted diffs, AI change summaries, extracted values, saved HTML, and pageAccess status to flag blocked or error pages.

Instructions

Get the full detail of one specific check by id: before/after screenshots, the highlighted difference, the AI summary of what changed, extracted values (current + previous), and the full HTML copy monity.ai kept of the page. 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>",
      "checkId": "<checkId>"
    },
    "name": "get_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)
checkIdYesCheck id (from get_check_history)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does substantial work: it describes the exact response payload and warns that when reachedContent is false the check hit a challenge, login, or error page and must not be reported as a content change. That is a genuine behavioral caveat an agent would otherwise misinterpret. It stops short of covering error cases, permissions, or size/pagination of the retained HTML.

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?

Two sentences, front-loaded with the core action and payload enumeration, followed by the interpretation rule. Dense but each clause carries information; the only minor cost is a long comma-chained list that is slightly harder to scan than a short bulleted enumeration would be.

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?

No output schema exists, so the description must explain what comes back, and it does so concretely (screenshots, diff, AI summary, extracted values, HTML copy) plus the meaning of pageAccess/reachedContent. For a two-parameter read tool with no annotations, nothing an agent needs to call and interpret it correctly is missing.

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 both parameters already document their provenance in the schema (monitor uuid from list_monitors, check id from get_check_history). The description adds no syntax, format, or validation meaning beyond "by id," so the baseline of 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?

"Get the full detail of one specific check by id" names a specific verb (get), a scoped resource (one check), and then enumerates the payload: screenshots, diff highlight, AI summary, extracted current/previous values, and HTML copy. This is far more than a restatement of the title "Get check detail" and lets an agent distinguish it from list-style siblings at a glance.

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?

The description tells the agent to use the id-chained flow implicitly via the schema (uuid from list_monitors, checkId from get_check_history) and gives an interpretive rule for the returned pageAccess/reachedContent fields. However, it never says when to pick this over siblings such as get_check_history or view_check_screenshot, so selection guidance is only implied.

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