Skip to main content
Glama
cloudbring

New Relic MCP Server

by cloudbring

list_apm_applications_rest

Retrieve a list of APM applications with optional filters for name, host, IDs, language, and pagination.

Instructions

List APM applications via REST v2.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_nameNo
filter_hostNo
filter_idsNo
filter_languageNo
pageNo
auto_paginateNo
regionNo

Implementation Reference

  • The `listApplications` method on `RestApmTool` executes the tool logic: builds a query from filter args, calls the REST API at '/applications' with optional pagination, and returns the results.
    async listApplications(args: ListApplicationsArgs): Promise<unknown> {
      const client = this.restFor(args.region);
      const path = '/applications';
      const query: Record<string, unknown> = {};
      if (args.filter_name) query['filter[name]'] = args.filter_name;
      if (args.filter_host) query['filter[host]'] = args.filter_host;
      if (args.filter_language) query['filter[language]'] = args.filter_language;
      if (args.filter_ids && args.filter_ids.length > 0)
        query['filter[ids]'] = args.filter_ids.join(',');
      if (args.page) query.page = args.page;
    
      const results: unknown[] = [];
      let nextUrl: string | undefined;
      let page = args.page;
      do {
        const res = await client.get<unknown>(path, page ? { ...query, page } : query);
        results.push(res.data);
        const next = res.links?.next;
        if (args.auto_paginate && next) {
          const u = new URL(next);
          const p = u.searchParams.get('page');
          page = p ? Number(p) : undefined;
          nextUrl = next;
        } else {
          nextUrl = undefined;
        }
      } while (args.auto_paginate && nextUrl);
    
      return { items: args.auto_paginate ? results : results[0], page };
    }
  • Type definition `ListApplicationsArgs` for the tool's input arguments (filters, page, auto_paginate, region).
    type ListApplicationsArgs = {
      filter_name?: string;
      filter_host?: string;
      filter_ids?: number[];
      filter_language?: string;
      page?: number;
      auto_paginate?: boolean;
      region?: Region;
    };
  • The `getListApplicationsTool` method returns the Tool definition with name 'list_apm_applications_rest' and inputSchema (type definitions for each argument).
    return {
      name: 'list_apm_applications_rest',
      description: 'List APM applications via REST v2.',
      inputSchema: {
        type: 'object',
        properties: {
          filter_name: { type: 'string' },
          filter_host: { type: 'string' },
          filter_ids: { type: 'array', items: { type: 'number' } },
          filter_language: { type: 'string' },
          page: { type: 'number' },
          auto_paginate: { type: 'boolean' },
          region: { type: 'string', enum: ['US', 'EU'] },
        },
      },
    };
  • src/server.ts:84-84 (registration)
    Tool registration: `restApm.getListApplicationsTool()` is added to the tools map during `registerTools()`.
    restApm.getListApplicationsTool(),
  • src/server.ts:187-190 (registration)
    The `executeTool` switch-case dispatches 'list_apm_applications_rest' to `new RestApmTool().listApplications(args)`.
    case 'list_apm_applications_rest':
      return await new RestApmTool().listApplications(
        args as Parameters<RestApmTool['listApplications']>[0]
      );
Behavior2/5

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

No annotations exist. Description only states it lists applications via REST v2, omitting behavioral details like pagination (via page/auto_paginate parameters), filtering capabilities, or response structure. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is very concise (one sentence) but underspecified. It lacks any structure like parameter descriptions or examples, making it too terse for a tool with 7 parameters.

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

Completeness1/5

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

With no output schema, no annotations, and 7 parameters, the description is far from complete. It does not explain return values, pagination behavior, or how filters interact. Inadequate for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds no information about the 7 parameters (e.g., filter_name, page, region). The tool relies entirely on the schema field names for meaning, which is insufficient.

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?

Description states verb 'List' and resource 'APM applications' via REST v2, making purpose clear. However, it does not explicitly differentiate from sibling 'list_apm_applications', though the 'REST v2' hint implies a distinction.

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 'list_apm_applications'. No prerequisites, caveats, or exclusions provided.

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

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