agent-cost-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_costA | Log token usage and cost for a task. Call this after each AI interaction. Args: model: Model name (e.g., 'claude-sonnet-4-6', 'gpt-5.4') tokens_in: Number of input tokens tokens_out: Number of output tokens task: Description of what the task was |
| cost_reportB | Get a spending report. Args: period: 'today', 'week', 'month', or 'all' |
| set_budgetA | Set daily and/or monthly budget limits. Args: daily_limit: Maximum daily spend in USD (0 = don't change) monthly_limit: Maximum monthly spend in USD (0 = don't change) |
| cost_trendB | Show daily spending trend as a text chart. Args: days: Number of days to show (default: 7) |
| supported_modelsA | List all supported models and their pricing. |
| estimate_costA | Estimate cost without logging it. Use for planning. Args: model: Model name tokens_in: Expected input tokens tokens_out: Expected output tokens |
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 6 tools
Each tool has a clear and distinct purpose: cost_report for spending summaries, cost_trend for daily trends, estimate_cost for planning, log_cost for recording usage, set_budget for limits, and supported_models for pricing info. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., cost_report, set_budget). Even 'supported_models' fits as a verb+noun. The naming is predictable and clear.
With 6 tools, the server is well-scoped for cost management—covering logging, estimating, reporting, budgeting, and model listing. This is a natural and complete set without being excessive.
The surface covers main cost operations: logging, estimating, reporting, trending, and budget setting. Minor gaps like viewing current budget limits or resetting budgets exist, but these are not critical for the core workflow.