New Relic MCP Server

by piekstra

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List Synthetic Monitors

list_synthetic_monitors

Retrieve all synthetic monitors from New Relic to review monitor coverage and status for your observability setup.

Instructions

List all synthetic monitors

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.3.2Nov 7, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / title
```
Removed value: -"list_synthetic_monitorsArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"list_synthetic_monitorsOutput"
```
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```
Changed1 schema field changedv1.0.0Jan 4, 2026
- addedInput schema / title
```
Added value: +"list_synthetic_monitorsArguments"
```
First observedNov 18, 2025

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about pagination, result limits, or ordering for a list operation that could return many monitors. The presence of an output schema covers the return shape, which is the only mitigating factor.

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?

A single front-loaded sentence with no wasted wording. It is as short as it can be, though it is arguably too terse to earn a top score.

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

Completeness3/5

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

For a zero-parameter list tool with an output schema, the description is minimally adequate: return values are documented elsewhere. Still missing is any note on pagination or expected result volume, which matters for a list of monitors.

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 zero parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly implies an unfiltered, no-argument listing.

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?

Names a specific verb ('List') and resource ('synthetic monitors'), and the plural form distinguishes it from the sibling get_synthetic_monitor. It does not, however, explicitly state scope boundaries such as whether all monitors or only active ones are returned.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance and never mentions the sibling get_synthetic_monitor for fetching a single monitor's details. The agent must infer the list-vs-get choice purely from the tool names.

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