nikhilnt
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_usageB | Log a single LLM API call with token counts. Call this after every Claude/GPT/Gemini response. |
| get_summaryC | Get token usage and cost summary for a time period. |
| set_budgetC | Set a spending budget with alert threshold. |
| list_sessionsC | List recent sessions with their cost and token totals. |
| list_modelsA | Show known models with their pricing per 1M tokens. |
| export_csvC | Export usage data as CSV text. |
| get_hintsA | Analyse your token usage and return ranked optimisation hints with estimated monthly savings. Call this any time you want actionable advice on reducing your AI spend. |
| get_hint_detailB | Get a deep-dive on a specific optimisation hint by its ID. |
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 8 tools
All eight tools have clearly distinct purposes: logging, summarizing, hinting, listing models/sessions, setting budgets, and exporting. No two tools overlap in functionality, ensuring unambiguous selection.
Tool names follow a consistent verb_noun pattern with lowercase underscores (e.g., list_models, set_budget, export_csv). No mixing of conventions or verb styles.
With eight tools, the server covers a focused domain (AI usage tracking and optimization) without being too sparse or overwhelming. Each tool serves a distinct and necessary function.
The tool surface covers core workflows: logging, viewing summaries, getting optimization hints, listing models/sessions, setting budgets, and exporting. Minor gap: no tool to delete or reset data, but the domain is primarily read-heavy and logging.