mcp-telemetry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| telemetry_jobsA | List all active and recently completed jobs across all connected MCP servers. |
| telemetry_job_statusA | Get the full status of a specific job — all steps, cost, and any failure reason. |
| telemetry_subscribeA | Watch live job events as they happen — blocks and streams inline progress until the job (or, with no jobId, the next job) finishes, or until timeoutMs elapses. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| telemetry-jobs | Live job state for all connected MCP servers. Subscribe to receive updates. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing jobs, getting detailed status of a specific job, and subscribing to live events. There is no overlap or ambiguity between them.
All tools share the 'telemetry_' prefix, but the naming patterns mix plural noun ('telemetry_jobs'), singular noun phrase ('telemetry_job_status'), and verb ('telemetry_subscribe'). This minor inconsistency prevents a perfect score.
With 3 tools, the server is slightly on the lean side but still provides the essential functions for monitoring telemetry jobs: list, detail, and subscribe. It feels appropriate for its focused scope.
The tool set covers the core workflows of viewing active/recent jobs, getting detailed status, and watching live progress. Minor gaps exist, such as lacking filtering or job management capabilities, but these are reasonable omissions for a simple monitoring server.