Skip to main content
Glama
xelber

New Relic MCP Server

by xelber

get-apm-metrics

Retrieve APM performance metrics including response time, throughput, error rate, and Apdex to monitor and troubleshoot application health.

Instructions

Get APM performance metrics for applications including response time, throughput, error rate, and Apdex. This provides a comprehensive overview of application performance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNameNoApplication name to filter metrics (optional)
timeRangeNoTime range (e.g., "1 HOUR AGO", "30 MINUTES AGO", "1 DAY AGO")1 HOUR AGO
metricsNoMetrics to retrieve

Implementation Reference

  • src/index.ts:144-172 (registration)
    Tool registration in ListToolsRequestSchema handler - defines the tool name, description, and input schema
    {
      name: 'get-apm-metrics',
      description:
        'Get APM performance metrics for applications including response time, throughput, error rate, and Apdex. ' +
        'This provides a comprehensive overview of application performance.',
      inputSchema: {
        type: 'object',
        properties: {
          appName: {
            type: 'string',
            description: 'Application name to filter metrics (optional)',
          },
          timeRange: {
            type: 'string',
            description: 'Time range (e.g., "1 HOUR AGO", "30 MINUTES AGO", "1 DAY AGO")',
            default: '1 HOUR AGO',
          },
          metrics: {
            type: 'array',
            items: {
              type: 'string',
              enum: ['responseTime', 'throughput', 'errorRate', 'apdex'],
            },
            description: 'Metrics to retrieve',
            default: ['responseTime', 'throughput', 'errorRate'],
          },
        },
      },
    },
Behavior2/5

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

No annotations provided, so description bears full burden. It only states 'comprehensive overview' without disclosing behavioral traits like read-only nature, data aggregation details, or default behavior when appName is omitted.

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 with no extraneous information. Directly states purpose and key included metrics.

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

Completeness2/5

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

With 3 optional parameters and no output schema, description lacks details on return format, default behavior (e.g., what happens if appName omitted), or how metrics are computed. Incomplete for full agent decision-making.

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% with descriptions for all 3 parameters. Description repeats enum values already in schema, adding no extra meaning or constraints beyond what is already structured.

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 verb 'Get', resource 'APM performance metrics', and lists specific metrics (response time, throughput, error rate, Apdex), distinguishing it from sibling tools like get-recent-logs or query-apm.

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?

No guidance on when to use this tool versus alternatives like query-apm or get-transaction-traces. Does not mention when not to use or provide decision criteria.

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/xelber/newrelic-mcp'

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