Skip to main content
Glama

Run a health check

run_health_check

Run a schema health check for a saved location: validates its markup, scans its website for the embed and conflicting hard-coded schema, detects unpublished changes and records the result in the dashboard and client reports. Needs a LocalSchema Pro API key in the request headers.

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": {
      "location_id": "<location_id>"
    },
    "name": "run_health_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
location_idYesLocation id from list_locations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / location_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true; the description earns credit by explaining both — it writes results into the dashboard and client reports, and it crawls the location's live website, which explains the open-world flag. It also discloses the auth requirement (LocalSchema Pro API key in request headers), which annotations cannot convey. Missing are any notes on scan latency, failure modes, or quota.

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?

Two sentences: the first front-loads the verb, the target resource, and the concrete sub-checks; the second carries the auth prerequisite. No filler, no repetition of the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should clarify what the caller gets back. It says the result is 'recorded in the dashboard and client reports' but never says whether the health-check findings are also returned in the response or must be fetched separately — a real gap for a non-idempotent write that triggers an external crawl. Everything else an agent needs (scope, auth, side effects) is present.

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 only one parameter and the schema covers it at 100% with a UUID pattern and a cross-reference to list_locations. The description adds no additional meaning about the parameter, so the schema does all the work — baseline 3 for high coverage.

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 a schema health check for a saved location') and then enumerates exactly what the check covers: markup validation, embed and hard-coded-conflict scanning, unpublished-change detection, and result recording. This is clearly distinguishable from siblings like validate_schema or validate_page, which validate artifacts rather than a saved location end-to-end.

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?

Usage is implied by the scope ('for a saved location' vs. the page/schema validators in the sibling set) and the prerequisite API key is given, but the description never explicitly says when to choose this over validate_schema or validate_page, nor any when-not conditions. The agent must infer the routing from the resource noun alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources