@originchain/telemetry-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OC_TELEMETRY_AGENT | No | Base URL of the telemetry agent | http://127.0.0.1:8892 |
| OC_TELEMETRY_TIMEOUT | No | Per-call timeout in milliseconds | 120000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_volumeA | Total log volume and distinct pattern count, instant from the rollup. |
| top_patternsC | The highest-volume log patterns, instant from the rollup. |
| similar_patternsA | Semantic (meaning-based) search over log patterns — finds related patterns even when they share no keywords. Query embedded server-side; returns cited matches. |
| recent_eventsA | The ACTUAL most-recent log lines (real values, not the / template), newest first — for 'what was the latest X', 'show the actual line', recent payment/auth/timeout events (ANY severity). Filter by service, severity, and/or a substring. For a loose 'error/problem' do NOT set severity=ERROR (those usually log as WARN); filter by service or contains. |
| recent_errorsA | Top ERROR/FATAL patterns in the last N minutes WITH the window's total volume, so 'no errors' is interpretable; also returns the actual recent error lines. |
| incident_analysisA | FLAGSHIP: one call fuses semantic cluster + latest occurrence (with the real log line) + trace causal chain + service graph + rate anomaly, cited. Use for compound incident questions. |
| service_graphA | Service dependency edges (who calls whom, call counts) from the maintained rollup. Pass a service for depends_on/called_by; omit for the whole graph. |
| fts_searchB | Full-text (BM25) keyword search over log template text. |
| trace_lookupB | All spans of one distributed trace, ordered by start time. |
| sql_queryA | One read-only SELECT for a specific filtered lookup. occurrences has a |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target clearly distinct concerns: aggregates, pattern search, raw lines, errors, traces, and dependency graphs. Some overlap exists between fts_search and similar_patterns, and between recent_events and recent_errors, but descriptions are explicit enough that an agent can disambiguate.
All names use lowercase snake_case and are mostly noun-phrase query names like log_volume, top_patterns, and service_graph. A few names like trace_lookup and sql_query hint at actions, so the pattern is not perfectly uniform, but it is readable and predictable.
Ten tools is well-scoped for a telemetry server. Each tool covers a distinct analytical need—aggregation, pattern search, raw log access, error analysis, incident synthesis, dependencies, traces, and SQL—without feeling bloated or redundant.
The surface covers the core telemetry workflow comprehensively: finding patterns, searching semantically and by keyword, inspecting actual log lines, analyzing errors, investigating entire incidents, tracing requests, and exploring service dependencies. The read-only SQL escape hatch also covers edge cases, so there are no obvious dead ends.