Skip to main content
Glama
cordlesssteve

Claude Telemetry MCP

get_telemetry_health

Check if the telemetry system is operational and accessible to monitor Claude usage metrics and analytics.

Instructions

Check if telemetry system is running and accessible

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main tool handler that invokes TelemetryService.isHealthy() and formats the markdown response with health status.
    case 'get_telemetry_health': {
      const isHealthy = await this.telemetryService.isHealthy();
      return {
        content: [
          {
            type: 'text',
            text: `## Telemetry System Health\n\n**Status**: ${isHealthy ? '✅ Healthy' : '❌ Unavailable'}\n\n${isHealthy ? 'Prometheus is accessible and telemetry data is being collected.' : 'Telemetry system is not responding. Check if services are running: `docker compose ps`'}`,
          },
        ],
      };
    }
  • src/index.ts:182-189 (registration)
    Tool registration in ListToolsRequestSchema response, specifying name, description, and empty input schema.
    {
      name: 'get_telemetry_health',
      description: 'Check if telemetry system is running and accessible',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Core implementation: PrometheusClient.isHealthy() performs HTTP GET request to Prometheus /-/healthy endpoint with 3s timeout and checks for 200 status.
    async isHealthy(): Promise<boolean> {
      try {
        const response = await axios.get(`${this.baseUrl}/-/healthy`, { timeout: 3000 });
        return response.status === 200;
      } catch {
        return false;
      }
    }
  • TelemetryService.isHealthy() method delegates the health check to the underlying PrometheusClient instance.
    async isHealthy(): Promise<boolean> {
      return await this.prometheus.isHealthy();
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool checks if the telemetry system is 'running and accessible,' which implies a read-only, diagnostic operation, but lacks details on what 'accessible' means, potential error conditions, response format, or any side effects. This is a significant gap for a tool with zero annotation coverage.

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?

The description is a single, clear sentence that front-loads the core purpose without any wasted words. It is appropriately sized for a simple, no-parameter tool, making it highly efficient and easy to parse.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but incomplete. It lacks context on what 'running and accessible' entails, expected outputs, or error handling, which are crucial for an agent to use it effectively. The absence of annotations and output schema means the description should compensate more.

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 has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, earning a baseline score of 4 for adequately handling the lack of parameters without unnecessary details.

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?

The description clearly states the tool's purpose with a specific verb ('Check') and resource ('telemetry system'), and specifies what is being checked ('running and accessible'). It distinguishes itself from sibling tools that focus on usage metrics rather than system health. However, it doesn't explicitly contrast with siblings like 'check_usage_limits' which might also involve system checks.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing, or context for checking telemetry health, nor does it reference sibling tools for related tasks like monitoring usage or capacity. Usage is implied only by the purpose statement.

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/cordlesssteve/claude-telemetry-mcp'

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