PingRelay MCP Server

integration_list

Read-onlyIdempotent

List integration configurations in the authenticated organization, including deleted and disabled integrations identified by IsDeleted and IsDisabled. Returns destinations and associated monitor/heartbeat names without pagination. Use MonitorNotificationsGet or HeartbeatIntegrationNotificationsGet to inspect selected notification routes.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description still adds real behavioral facts beyond them: deleted/disabled items are included, and results are unpaginated (one full list). It stops short of return size/cost hints or auth requirements, which keeps it from a 5.

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 the listing scope, then the payload contents, then the alternative routing. Every sentence carries distinct information and nothing is repeated from the name or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Zero parameters, no output schema, and the description compensates by describing the returned entities (destinations plus monitor/heartbeat names) and the deleted/disabled inclusion semantics. There is no output schema to defer to, yet the agent still knows what comes back and what it cannot do here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no input parameters, so per the baseline this dimension starts at 4. Nothing in the description contradicts or complicates the empty schema, and no parameters are left undocumented.

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 ("List integration configurations") plus the exact scope ("in the authenticated organization") and explicitly notes that soft-deleted and disabled records are included, flagged via IsDeleted/IsDisabled. It also says what the payload contains (destinations, associated monitor/heartbeat names), so an agent can distinguish it from integration_get and the notification-route siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names two concrete alternatives (MonitorNotificationsGet, HeartbeatIntegrationNotificationsGet) and the condition that selects them: inspecting selected notification routes. This is an explicit routing rule, not an implied one, and it is paired with the enumeration scope of this tool.

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

All PingRelay MCP Server tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?