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
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
agentsB

Spend per sub-agent type: runs, the model it mostly used, average cost per run, the share of runs whose tool calls were all read-only, errored tool results, and runs where the requested model differed from the one actually used.

changesB

Every point where a sub-agent's model changed, with the real runs before and after compared and a verdict: keep, watch, revert, or too early. These are measured figures, not estimates.

findingA

One finding in full, addressed by its stable id from report: what happened, why it costs, what to change, what to expect, plus the evidence table and the patch if there is a file to change.

pricesA

The price table every figure is computed from, in US dollars per million tokens, with the date it was last verified. Includes any overrides from the user's config.

refreshA

Rescan the transcript directories now instead of waiting for the automatic rescan, and report how many files were scanned, newly recorded, unchanged, or skipped. Only tallybook's own database is written.

reportA

What the coding agents on this machine cost over a window: the total, the split by tool and by model, and the list of findings about what would have been cheaper. Call finding with an id from the list for the full advice.

sessionA

One session turn by turn: model, effort, token counts and cost per model response. Accepts a full session id or a unique prefix. Never returns prompt text, tool output, or command lines; the database does not hold them.

sessionsA

Sessions in the window with what each cost, sorted by cost or by time, most expensive or most recent first. Includes sub-agent runs as their own rows.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target distinct facets: report (aggregate), sessions (list), session (single), agents (sub-agent breakdown), changes (model-change points), finding (one finding), prices, refresh. The main risk is report vs sessions vs agents overlapping in cost-summary territory, and session vs sessions differing only by plural, but descriptions clearly separate them.

Naming Consistency4/5

All names are single lowercase nouns (agents, changes, finding, prices, refresh, report, session, sessions), so the convention is applied consistently. The only weakness is session/sessions and agents/sessions reading similarly, which slightly hurts predictability.

Tool Count5/5

Eight tools is well-scoped for a cost-tracking server, with each tool mapping to a clear function (scan, price table, aggregate report, listing, drill-down, sub-agent detail, model-change tracking, findings). Nothing appears redundant or padded.

Completeness5/5

The surface covers the full lifecycle: refresh to ingest data, prices for computation basis, report/sessions/agents for aggregate and sub-agent views, session for turn-level drill-down, changes for model change comparisons, and finding for full advice with evidence. No obvious gaps or dead ends for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues