Skip to main content
Glama

check_site_health

Read-only

Loads the site's key pages and boots WordPress to confirm the site is up and report any fatal errors.

Instructions

Load the site's key pages and boot WordPress now: is the site up, any fatal errors?

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": "check_site_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds that it actually loads key pages and surfaces fatal errors, which is useful. However, 'boot WordPress' is ambiguous and can read as an initializing/mutating action, and nothing says how expensive or slow loading multiple pages is.

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?

A single compact sentence with the action front-loaded and the diagnostic question at the end. The phrasing ('boot WordPress now:') is slightly loose but nothing is redundant.

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 and one undocumented parameter, the description should say more about what a result looks like (error list vs. up/down status) and how the target site is chosen. It covers the intent but leaves the calling mechanics underspecified.

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

Parameters2/5

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

There is one parameter ('site') with 0% schema description coverage, and the description never mentions it — it does not say whether omitting it targets the current/default site or what values are accepted. The description therefore does not compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a concrete action ('Load the site's key pages') with a clear diagnostic question ('is the site up, any fatal errors?'), so the agent knows this is a health/availability check. It does not name a sibling it should be preferred over (e.g. site_overview or wp), so differentiation is left implicit.

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?

'boot WordPress now' implies this is the go-to check when something appears broken or immediately after a change, but there is no explicit when-to-use/when-not statement and no named alternative such as site_overview for general status.

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