PingDeck Uptime Monitoring

Check if a website is up

check_website

Read-onlyIdempotent

Check now if a website or a URL is up or down. The answer has the HTTP status, the response time and a plain verdict: up, down, reachable_but_refused or page_error. It is a real request from a PingDeck server in Singapore at the time of the call, not a stored value. No account and no API key are necessary.

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": {
      "url": "<url>"
    },
    "name": "check_website"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	A URL or a domain, for example https://example.com/health or example.com.
`api_key`	No	Optional. A PingDeck API key (pd_live_...). Without a key the check uses the free pool: 100 checks a day for each IP address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so safety is covered; the description adds genuinely new context by disclosing that the request originates from a Singapore-based PingDeck server at call time and that no account or API key is required.

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?

Four short sentences, front-loaded with the purpose, then the return contents, then the freshness guarantee and auth requirement; nothing is redundant and every sentence adds information.

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 return-value burden and does so by naming HTTP status, response time and the four verdict values. A brief note on verdict meanings or rate-limit behavior on failure would close the remaining gap.

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%, so both parameters are already documented in the schema, including the free-pool rate limit. The description only echoes the no-key-needed point and adds no format or syntax detail beyond it, so the 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 and resource ('Check now if a website or a URL is up or down') and enumerates the possible verdicts, which makes it distinguishable from adjacent tools like check_ssl or dns_lookup without opening any schema.

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?

'Check now' and 'at the time of the call, not a stored value' imply a real-time live-check use case, but no alternative tool is named and there is no explicit when-not-to-use guidance (e.g. versus check_ssl or service_status).

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

All PingDeck Uptime Monitoring tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?