Skip to main content
Glama

Pagetool

Check a published site the way a visitor and a crawler see it

live_check
Read-onlyIdempotent

For a published domain of your site: https root 200, http and www reach https:/// in one hop, title/description/og tags name the site, og:image is a 1200x630 PNG/JPEG, the favicon is the site's own, no editor leftovers, outbound links answer, exactly one h1, no draft badge. Returns PASS/WARN/FAIL per check. stored:true returns the automatic report made about two minutes after publish_site.

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": {
      "domain": "<domain>"
    },
    "name": "live_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe person or business the title and og tags must name. Defaults to the site name.
domainYesThe published domain to check, e.g. "angelamcgraw.com".
storedNotrue = return the newest stored report (including the automatic one ~2 minutes after publish_site) without fetching.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered; the description adds real value on top by disclosing the return shape (PASS/WARN/FAIL per check) and the timing semantics of the stored report. It does not mention fetch latency, rate limits, or what happens when the domain is unreachable, which are the remaining behavioral gaps.

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?

Front-loaded with the object of the check and dense with concrete assertions, with no filler sentences. The long comma-spliced check list is efficient but reads as an undifferentiated run-on, making it slightly harder to scan than a structured list would be.

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 correctly carries the burden by stating the PASS/WARN/FAIL-per-check return format and the two operating modes (live fetch vs stored). For a read-only, open-world checker this is nearly complete; only severity interpretation and failure modes are left implicit.

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 coverage is 100%, so all three parameters are already documented with their defaults and examples. The description restates the stored:true behavior (newest stored report, no fetching) but adds no new meaning about the name parameter's matching rules or the domain format beyond what the schema says. Baseline 3 applies.

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 names a specific verb (check) and a precisely scoped resource (a published domain of your site), then enumerates the exact conditions verified: https root 200, http/www one-hop redirect, title/og tags, og:image dimensions and format, favicon ownership, no editor leftovers, outbound links, single h1, no draft badge. This is unmistakably distinct from publish_site or site_stats.

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 rather than stated: 'For a published domain of your site' signals this runs after publishing, and the mention of the automatic report '~2 minutes after publish_site' hints at the post-publish moment. However, it never explicitly says when to prefer this over publish_status or site_stats, and offers no when-not guidance.

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