Claude Telemetry MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_session_usageB | Get usage metrics for the current Claude Code session (tokens, cost, activity) |
| get_today_usageB | Get total usage metrics for today (tokens, cost, sessions, activity) |
| get_week_usageB | Get total usage metrics for the current week (Monday-Sunday) |
| get_usage_summaryB | Get comprehensive usage summary for session, today, and this week in one call |
| check_usage_limitsB | Check current usage against specified limits and get warnings |
| get_usage_warningsB | Get usage warnings with default thresholds (80% and 90% of typical limits) |
| estimate_remaining_capacityC | Estimate remaining usage capacity for specified daily/weekly limits |
| get_usage_trendsC | Get usage trends over time to identify patterns |
| get_session_analyticsB | Get analytics about session patterns (averages, totals, productivity metrics) |
| get_tool_usage_breakdownB | Get breakdown of tool usage and edit decisions |
| compare_usage_periodsC | Compare usage between different time periods |
| get_telemetry_healthB | Check if telemetry system is running and accessible |
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 12 tools
The tools have overlapping purposes that could cause confusion, particularly around usage retrieval. For example, get_today_usage, get_week_usage, get_current_session_usage, and get_usage_summary all provide usage metrics with unclear boundaries between them. However, descriptions help differentiate some tools like compare_usage_periods and get_usage_trends.
Most tools follow a consistent verb_noun pattern (e.g., get_usage_summary, check_usage_limits, estimate_remaining_capacity), which is predictable and readable. There are minor deviations like compare_usage_periods (verb_noun_noun) and get_telemetry_health, but overall the naming is coherent.
With 12 tools, the count is reasonable for a telemetry server focused on usage monitoring and analytics. It's slightly on the higher side but still well-scoped, as each tool appears to serve a distinct analytical function without obvious redundancy.
The tool set provides comprehensive coverage for telemetry and usage analytics, including current metrics, historical trends, comparisons, capacity estimation, and health checks. There are no obvious gaps; agents can monitor, analyze, and manage usage effectively without dead ends.