- 3 minutes to read

MCP Tools for Monitoring and Logging

These five groups answer the operational questions: is the MCP Endpoint healthy, which Monitor Views and Log Views exist, which Integrations they cover, and what failed recently. Every tool here only reads. They are the first five groups in the Tools picker of the AI Assistant, and all of them are selected by default.

  • ✅ 21 read tools in five groups
  • ✅ One OAuth scope per group
  • ✅ Failed logged events summarized by Integration, System, or Service

The MCP Tool Reference explains the scopes, the paging rules, and the other groups.

Understanding the Groups

Group Tools OAuth scope Use it to
Health 1 None; any authenticated caller Check that the server runs
Monitor Agents 3 mcp:monitoragents.read Find Monitoring Agents, which the tools call sources
Monitor Views 5 mcp:monitorviews.read Find Monitor Views and what they cover
Integrations 6 mcp:integrations.read Find Integrations and their Services, Systems, and Contracts
Log Views 6 mcp:logviews.read Find Log Views, and the failed logged events in a time window

Inputs are camelCase. take and skip follow the common paging rules.

Health (1)

Tool What it does Inputs
health Server health (Healthy, Degraded, or Unhealthy), component checks, uptime, and version None

Monitor Agents (3)

Tool What it does Inputs
get_source_by_name One Monitoring Agent by its exact name name
list_sources All Monitoring Agents, page by page take, skip
search_sources Monitoring Agents by part of a name term, take, skip

Monitor Views (5)

Tool What it does Inputs
explain_monitor_view A deep drill-down into one Monitor View: health details and full scope name
get_monitor_view_by_name One Monitor View by its exact name (active, not deleted) name
list_monitor_views Monitor Views, page by page (active, not deleted) take, skip
list_monitor_views_with_integration_metadata Monitor Views that contain Integrations with matching Custom Metadata metadataValueSubstring, take, skip
search_monitor_views Monitor Views by part of a name (active, not deleted) term, take, skip

Integrations (6)

Tool What it does Inputs
explain_integration A deep drill-down into one Integration's full architecture name
get_integration_by_name One Integration by its exact name name
get_integration_with_relationships One Integration with its Services, Systems, and Contracts name
list_integrations All Integrations, page by page take, skip
list_integrations_with_metadata Integrations whose Custom Metadata matches a substring metadataValueSubstring, take, skip
search_integrations Integrations by part of a name term, take, skip

Log Views (6)

Tool What it does Inputs
explain_log_view A deep drill-down into one Log View and the activity it scopes name
get_failed_log_event_summary Which Integrations, Systems, or Services had failed logged events in a time window, with counts groupBy, period, from, to, timeZone, name, take, skip
get_log_view_by_name One Log View by its exact name (active, not deleted) name
list_failed_log_events The failed logged events in a time window, newest first integrationName, systemName, serviceName, period, from, to, timeZone, take, skip
list_log_views Log Views, page by page (active, not deleted) take, skip
search_log_views Log Views by part of a name (active, not deleted) term, take, skip

list_failed_log_events returns 20 events by default, and skip plus take may not exceed 1000. Above that, the tool refuses the call with a message that says so.

Next Steps