Skip to main content
Glama
thrashy

New Relic MCP Server

by thrashy

create_service_level

Create a service level indicator (SLI) on an entity to define and monitor service level objectives (SLOs) using NRQL event queries and target thresholds.

Instructions

Create a Service Level Indicator on an entity. For SLIs over OTEL distribution metrics (FROM Metric), never use function COUNT (it counts pre-aggregated data points, not requests): use GET_FIELD for availability and GET_CDF_COUNT with a threshold for latency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_guidYesGUID of the entity to attach the SLI to
nameYesSLI name
descriptionNoSLI description (optional)
eventsYesSLI event queries. Provide validEvents plus either goodEvents or badEvents.
objectivesYesSLO objectives, e.g. [{target: 99.9, timeWindow: {rolling: {count: 28, unit: DAY}}}]
account_idNoAccount ID (optional)
Behavior3/5

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

No annotations provided; description warns about function choice for OTEL metrics but lacks details on side effects, permissions, or rate limits.

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?

Two concise sentences front-loading purpose and critical warning. No wasted words.

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?

No output schema, so return values are not explained. Lacks prerequisites or error context, but the core purpose and a key usage caution are present.

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?

Schema coverage is 100% (baseline 3). Description adds valuable rule ('never use COUNT for OTEL metrics') that clarifies function selection beyond schema descriptions.

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?

Clearly states it creates an SLI on an entity. Differentiates from sibling tools (delete, get, list, update) by action verb.

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?

Usage is implied by name and action; provides specific guidance for OTEL distribution metrics, but does not explicitly mention when to avoid using this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thrashy/mcp-newrelic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server