Pingstack

Get heartbeat ping URLs

get_check_ping_urls

Read-onlyIdempotent

Read the ping URLs of a heartbeat (ping) check, one per heartbeat location, with each location's name. A job reports in by requesting its URL, so each URL works as a secret credential. Only heartbeat checks have ping URLs; other kinds return invalid_kind. Needs the checks:ping_urls permission, which is off unless granted when the connection is approved.

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": {
      "id": "<id>"
    },
    "name": "get_check_ping_urls"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Heartbeat (ping) check id (check_…).

Output Schema

Name	Required	Description	Default
`id`	Yes
`locations`	Yes
`sensitive`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive safety profile, and the description adds genuinely new behavior: each URL is a secret credential, the invalid_kind failure mode, and a permission (checks:ping_urls) that is off by default. Those are exactly the facts an agent needs before calling and before echoing results.

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?

Three short sentences, front-loaded with what is returned, followed by the security caveat, the error case, and the permission gate. No filler or repetition.

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?

An output schema exists, so return values need no explanation, and the description still covers sensitivity, failure mode, and auth prerequisites. The only gap is that it never points at a sibling for non-heartbeat checks, a minor omission for a single-parameter read tool.

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% and the single id parameter is fully documented in the schema, so the baseline applies. The description restates the resource type but adds no format or validation meaning beyond what the schema already declares.

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?

States a specific verb and resource ('Read the ping URLs of a heartbeat (ping) check') plus the shape of the result ('one per heartbeat location, with each location's name'). The clause that only heartbeat checks have ping URLs cleanly separates it from the broader get_check tool.

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?

Gives a clear precondition and a when-not condition: other check kinds return invalid_kind, so the agent knows not to call this for non-heartbeat checks. It does not explicitly route to siblings such as get_check for other check kinds, leaving that inference to the agent.

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

All Pingstack 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?