runmeter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNMETER_DB_PATH | No | SQLite telemetry store location | ~/.runmeter/runmeter.db |
| RUNMETER_PRICING | No | JSON 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
| 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 |
|---|---|
| runmeter_recordA | Record a single LLM/agent run and return the stored row. Cost is taken from |
| 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 |
| runmeter_summaryA | Aggregate telemetry into cost and reliability rollups. group_by is one of: 'model', 'agent', 'finish_reason', 'day', or 'tag'.
Optional |
| runmeter_exportA | Export raw runs as a JSON array or CSV string for external analysis. fmt is 'json' or 'csv'. Optional |
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Aptica-Solutions/a-mcp-runmeter'
If you have feedback or need assistance with the MCP directory API, please join our Discord server