Skip to main content
Glama
Aptica-Solutions

runmeter

by Aptica-Solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RUNMETER_DB_PATHNoSQLite telemetry store location~/.runmeter/runmeter.db
RUNMETER_PRICINGNoJSON file overriding/extending per-model pricing

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
runmeter_recordA

Record a single LLM/agent run and return the stored row.

Cost is taken from cost_usd when provided; otherwise it is computed from the built-in pricing table (USD per 1M tokens) when the model is known. If the model is unpriced and no cost is given, cost is stored as null and the response notes that the model is unpriced so you can extend the table.

runmeter_getA

Return the full stored row for a single run id.

runmeter_listA

List runs newest-first with optional filters.

Filters: model, agent, status ('ok'/'error'), tag (matches any run carrying that tag), and since (ISO timestamp or relative window like '24h', '7d'). Use limit/offset to page. Returns up to limit rows plus the total count matching the filters so you know whether to page further.

runmeter_summaryA

Aggregate telemetry into cost and reliability rollups.

group_by is one of: 'model', 'agent', 'finish_reason', 'day', or 'tag'. Optional since limits the window (ISO timestamp or relative like '30d'). Each group reports run count, total input/output tokens, total cost, average latency, and error rate. Groups are sorted by total cost descending.

runmeter_exportA

Export raw runs as a JSON array or CSV string for external analysis.

fmt is 'json' or 'csv'. Optional since limits the window. Newest-first, capped at limit rows (max 10000).

runmeter_deleteA

Delete a single run by id. Requires confirm=true to actually remove it.

This is the only destructive tool. It scopes to one id and refuses to run without an explicit confirm, so it cannot wipe the store by accident.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct operation: recording, retrieving a single run, listing with filters, aggregating summaries, exporting, and deleting. There is no overlap in purpose, making tool selection unambiguous.

Naming Consistency5/5

All tool names follow the pattern 'runmeter_' + verb (get, summary, record, list, export, delete). The consistent prefix and verb-based naming make the toolset predictable and easy to navigate.

Tool Count5/5

Six tools is well within the ideal 3-15 range and perfectly scoped for a telemetry server. Each tool earns its place, covering core operations without unnecessary bloat.

Completeness5/5

The toolset covers the full lifecycle of LLM/agent run telemetry: record, retrieve, list, analyze, export, and delete. There are no obvious missing operations for the domain, and the single-run delete with confirmation prevents accidental data loss.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources