Skip to main content
Glama

Site health

get_site_health
Read-only

The hourly SEO checkup of the website: each check passing or failing with details, and recent activity. The first call starts the first check.

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

Input Schema

NameRequiredDescriptionDefault
domainNoThe website's domain, e.g. acme.com. Leave out to use the account's website.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety is already covered; the description adds genuinely non-obvious behavior: the first call actually kicks off a check rather than only reading stored state, and results are refreshed hourly. It does not say how long a check takes or whether a freshly triggered call returns partial results, which is the main remaining behavioral gap.

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?

Two short sentences with no filler, and the content shape is front-loaded before the side-effect note. The final clause about the first call is slightly cryptic — it isn't explicit whether it triggers a crawl or just unpacks results — which costs a point on clarity rather than length.

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?

With no output schema, the description carries the burden of describing returns, and it does so at a useful level (per-check status, details, recent activity). For a read-only reporting tool with one optional parameter, that is close to sufficient; only check latency and the freshness/partial-result caveat are missing.

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% on the single optional `domain` parameter, including the fallback to the account's website, so the schema already carries the semantics. The description adds nothing about the domain parameter, so the baseline 3 applies.

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 hourly SEO checkup of the website: each check passing or failing with details, and recent activity" names the resource (site health), the granularity (per-check pass/fail), and the payload (details + recent activity). It reads as a noun phrase rather than a verb, but an agent can tell this returns a health report rather than raw analytics like get_search_performance or get_visitors.

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 only implied: the agent must infer this is the tool for 'how is my site doing' questions, and there is no explicit routing to or away from siblings such as get_dashboard, list_fixes, or fix_now, which plausibly overlap. The one concrete timing cue — "The first call starts the first check" — is a helpful usage note but not a when-to-use rule.

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