PingRelay MCP Server

monitor_notifications_get

Read-onlyIdempotent

Get a non-deleted monitor's effective state and all non-deleted organization integrations, including unselected and disabled integrations. Integration IsChecked means assigned to this monitor, not necessarily enabled; integration IsDisabled indicates a disabled integration, while top-level IsDisabled indicates a disabled monitor. Does not return user-specific notification preferences.

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": {
      "monitorExternalId": "<monitorExternalId>"
    },
    "name": "monitor_notifications_get"
  }
}

Input Schema

Name	Required	Description	Default
`monitorExternalId`	Yes	External monitor GUID returned as Id by MonitorList or MonitorListRecent.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint false), yet the description adds real behavioral context: which entities are excluded (deleted monitors, deleted integrations, user-specific preferences) and how two differently-scoped IsDisabled flags differ. It does not state failure behavior for a non-existent or deleted monitorExternalId, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the returns-what statement, then the semantic disambiguation of the two IsDisabled flags, then the exclusion. Dense but every clause carries information; nothing is padding.

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?

There is no output schema, so the description correctly spends its space explaining the shape and meaning of returned fields, including the IsChecked/IsDisabled distinction. Given a one-parameter read tool, an agent has nearly everything needed; only error behavior and ordering/pagination of integrations are unaddressed.

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 parameter's description already explains where the GUID comes from (MonitorList / MonitorListRecent), so the description adds nothing about the parameter and properly does not need to. The baseline of 3 applies.

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?

States a specific verb ('Get') and a precise resource set: a non-deleted monitor's effective state plus all non-deleted organization integrations. The scope qualifiers ('including unselected and disabled integrations', 'non-deleted') make it concrete, though no sibling tool is named as a contrast, which would have fully separated it from monitor_get and heartbeat_integration_notifications_get.

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 by the content description rather than stated: an agent can infer this is the tool for monitor-level integration assignment state. There is no explicit 'use X when...' guidance, and the negative sentence ('Does not return user-specific notification preferences') hints at a boundary without naming the alternative tool such as heartbeat_integration_notifications_get.

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?