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.

pricesB

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.7/5.0

Scored across 8 tools

Disambiguation4/5

Each tool targets a distinct granularity: report (window summary), sessions (per-session list), session (single session detail), agents (per-agent-type rollup), changes (model-change points), finding (single finding), prices, and refresh. The analytics tools (report/sessions/agents/changes) overlap in domain and an agent must parse descriptions carefully to pick the right level, but boundaries are stated clearly enough.

Naming Consistency4/5

Seven tools are single lowercase nouns (finding, prices, agents, changes, session, report, sessions) with only refresh acting as a verb, so the set is mostly predictable despite lacking a verb_noun pattern. The session/sessions singular-plural pair is a minor readability risk but conventional.

Tool Count5/5

Eight tools is well-scoped for a cost-tracking server: one data-refresh action, one price reference, and a small hierarchy of correctly-sized analytics views. No tool feels redundant or bolted on.

Completeness4/5

The read/analytics surface is thorough (window totals, session and sub-agent breakdowns, change verdicts, drill-down findings, price reference, manual rescan). Minor gaps exist: no tool to set or edit the price/override config that 'prices' reads from, and no keyword search across findings.

Maintenance

ActivityMaintained
ResponsivenessNo issues