Skip to main content
Glama

Pagetool

Check whether a domain is live

publish_status
Read-onlyIdempotent

For a domain your site uses: does DNS point at our server, is the HTTPS certificate in place, and does the page answer? live:true means a visitor can open https:// now. A fresh domain usually takes 5-15 minutes; poll every 20-30 seconds.

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

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to check, e.g. "heapy.net". Poll every 20-30 seconds after publish_site until live is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the three underlying checks, the exact meaning of a true result, typical propagation latency, and recommended poll interval. It never contradicts the read-only annotation, and it omits what a false result looks like (no per-check detail), which is the main remaining gap.

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 tight sentences, front-loaded with the checks and their result semantics, followed by the timing guidance an agent actually needs. No filler and no repetition of the tool name or title.

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?

For a single-parameter, read-only probe with no output schema, the description covers what is checked, what true means, and how long to wait before polling. It is slightly incomplete in that it does not describe the negative case or whether per-check diagnostics are returned.

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?

The single 'domain' parameter has 100% schema description coverage, including an example and the polling instruction, so the schema carries most of the load. The description only adds that the domain should be one your site uses; with coverage this high, the baseline of 3 is appropriate.

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 names the concrete checks performed (DNS points at our server, HTTPS certificate in place, page answers) and defines the outcome field ('live:true means a visitor can open https://<domain> now'). It does not contrast itself with the sibling live_check, so an agent cannot tell from the text alone which of the two liveness-style tools to pick.

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?

It gives clear operating context: 'For a domain your site uses', plus timing expectations (5-15 minutes for a fresh domain) and a polling cadence (every 20-30 seconds). It stops short of explicit when-not-to-use guidance or naming an alternative tool, so no exclusions are stated.

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