Skip to main content
Glama

Get latest result

get_latest_result

Retrieve a monitor's last completed check with status, alert flag, extracted values, AI summary, page-access state, and artifact links to see what a page shows now or whether it changed.

Instructions

Get a monitor's most recent completed check: status, whether it alerted, the extracted output (current and previous value), AI summary, and artifact URLs (screenshots, diff image, HTML snapshot). This answers questions like 'what is the price now?' or 'did anything change?'. 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_latest_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)

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 useful work: it discloses that artifact URLs (screenshots, diff image, HTML snapshot) come back, and it explains the pageAccess/reachedContent semantics so the agent doesn't misreport a challenge or login page as a content change. It omits what happens when there is no completed check yet, and any auth/permission expectations.

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 sentences, front-loaded with purpose then return contents then an interpretation caveat. Dense but every clause carries information; the field enumeration is long but justified because there is no output schema.

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?

No output schema exists, so the description must explain the return shape and it does so thoroughly, including the tricky pageAccess/reachedContent interpretation rule. Remaining gaps are the empty/no-completed-check case and whether artifact URLs expire, which are minor for a single-parameter read.

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?

There is one parameter and the schema already documents it at 100% coverage ('Monitor uuid (from list_monitors)'). The description adds no additional meaning about the uuid, so the baseline 3 for a fully covered schema 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?

Specific verb (get) plus precise resource and scope: 'a monitor's most recent completed check'. It then enumerates the returned payload (status, alert flag, current/previous extracted value, AI summary, artifact URLs), which distinguishes it from the history-listing siblings without needing to name them.

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?

It gives clear usage context with example questions ('what is the price now?', 'did anything change?'), which tells the agent when this is the right call. It never names an alternative such as get_check_history or get_recent_changes, so the when-not guidance is left implicit.

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