watchgoose-mcp

List a check's status changes

list_flips

Read-onlyIdempotent

List a check's status-change history, newest first, with optional time filters. See when a check became up (up=1) or entered states like down, paused, or resumed.

Instructions

List retained status changes for a check, newest first, with optional time filters. In results, up: 1 means the check became up; up: 0 means any other status, including down, paused, and new after resume. A pause or resume that changes the check's status records a flip.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	No	Exclusive upper bound for status-change timestamps, as Unix seconds; for example 1592217980.
`limit`	No	Maximum number of status changes to return, from 1 to 200.
`start`	No	Inclusive lower bound for status-change timestamps, as Unix seconds; for example 1592214380.
`seconds`	No	Lookback window for status changes in seconds, from 0 to 31536000; for example 3600.
`unique_key`	Yes	40-character stable check identifier from list_checks.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes
`flips`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.1Sep 4, 2026

addedInput schema / properties / end / description

Added value: +"Exclusive upper bound for status-change timestamps, as Unix seconds; for example 1592217980."

addedInput schema / properties / limit / description

Added value: +"Maximum number of status changes to return, from 1 to 200."

addedInput schema / properties / seconds / description

Added value: +"Lookback window for status changes in seconds, from 0 to 31536000; for example 3600."

addedInput schema / properties / start / description

Added value: +"Inclusive lower bound for status-change timestamps, as Unix seconds; for example 1592214380."

addedInput schema / properties / unique_key / description

Added value: +"40-character stable check identifier from list_checks."

First observedv1.0.0Sep 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description explains key output semantics: up: 1 means became up, up: 0 includes down/paused/new-after-resume, and pause/resume that changes status records a flip. This materially helps an agent interpret results and is not visible in the schema alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the core operation, followed by the essential semantics of the up field and flip recording. Every sentence contributes useful information with no redundancy.

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?

With annotations and an output schema present, the description sufficiently covers what the tool returns, how results are ordered, and what counts as a flip. The required unique_key and optional time filters are documented in the schema, so nothing critical is missing for invoking the tool correctly.

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 the schema already documents all five parameters. The description adds only the general notion of 'optional time filters,' which aligns with start/end/seconds but provides no additional parameter-level meaning beyond the schema.

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?

The description uses a specific verb and resource: 'List retained status changes for a check.' It also states the ordering ('newest first') and clearly distinguishes this tool from siblings by focusing on status-change history rather than listing checks or fetching a single check.

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 gives clear context: use this when you need a check's status changes with optional time filters. It does not explicitly name alternatives or say when not to use it, but the operation is distinct enough from list_checks and get_check that the intended use is evident.

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

Deploy Server