Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
estimate_llm_costB

Estimate one LLM request from supplied per-million token rates. Input tokens include cached tokens.

analyze_llm_usageB

Analyze normalized LLM usage; report costs, unknown models and conditional response-cache opportunities. No network or file access.

compare_llm_modelsC

Compare a target model with known-price baseline. Scenario only; requires quality evaluation and does not change routing.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 3 tools

Disambiguation4/5

Each tool targets a different scope: single-request estimation, aggregate usage analysis, and model comparison. They all relate to cost, but the descriptions make the boundaries clear enough for an agent to select correctly.

Naming Consistency5/5

All three names follow the same verb_llm_noun pattern: estimate_llm_cost, analyze_llm_usage, compare_llm_models. The convention is predictable and consistent.

Tool Count5/5

Three tools are well-scoped for a narrow cost-analysis server, and each serves a distinct purpose. No unnecessary tools are present.

Completeness3/5

The surface covers estimation, usage analysis, and model comparison, but an optimizer would benefit from a recommendation or pricing-catalog operation. As named, it analyzes costs rather than completing an optimization lifecycle.

Maintenance

ActivityMaintained
ResponsivenessNo issues