Skip to main content
Glama
surplus-auctions-mcp

surplus-auctions-mcp

Check that GovDeals still works

health_check
Read-only

Run live canary checks against GovDeals for every tool, reporting pass, degraded, or fail with the reason so you can diagnose SITE_CHANGED errors or suspicious results.

Instructions

Run live canary checks against GovDeals for every tool and report pass / degraded / fail with the reason. Use when a tool returns SITE_CHANGED or results look wrong. Takes 30–90 seconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "health_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
checksYes
overallYes
checked_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered by structured data. The description adds genuinely new behavior: the check is live (real network calls against the external site), it spans every tool rather than one, and it carries a 30–90 second latency cost — that last point is critical for an agent deciding whether to block on it.

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?

Three sentences, each earning its place: what it does, when to call it, and how long it takes. The duration note is placed last where it acts as a practical caveat rather than burying the main purpose.

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?

An output schema exists, so return-value detail is not the description's job. For a zero-parameter tool with full annotation coverage, the description supplies the remaining gaps — external liveness, coverage breadth, and latency — leaving nothing an agent needs in doubt before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no schema content the description needs to amplify. The description correctly signals that scope is implicit (all tools) rather than configurable, which tells the agent no arguments are expected.

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 — 'run live canary checks against GovDeals for every tool' — plus the output shape (pass / degraded / fail with reason). No sibling would be confused with this, since compare_auctions, get_auction_details, list_ending_soon, and search_auctions are all data-retrieval tools whereas this is a diagnostic.

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?

Gives a concrete trigger condition: 'Use when a tool returns SITE_CHANGED or results look wrong.' That is a clear, actionable when-to-use signal tied to a specific error code. It stops short of a 5 because it offers no when-not guidance (e.g. don't run it preemptively on every request) and names no alternative diagnostic path.

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