agentic-ledger
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsA | List recent agent sessions with aggregated stats — call count, total cost, token usage, and start time. Use this to find a session_id before calling get_session or to get a cost overview. |
| explainA | Retrieve the full captured trace for a single LLM call. Returns the prompt, system prompt, tool calls, model response, token usage, cost, and latency. |
| get_sessionA | Retrieve the LLM calls of an agent session in chronological order. By default each call is a compact summary (index, model, status, error reason, tokens, cost, latency, tool names, sizes) — sessions can be megabytes, so full prompt/response bodies are returned only with include_messages=true, and single calls are better fetched via the explain tool using the action_id from a summary row. |
| searchA | Full-text search across all captured LLM calls. Searches prompts, outputs, system prompts, agent names, and user IDs. Use this to find calls related to a topic, error, or agent. |
| list_runsA | List loop runs (explicit x-agenticledger-run-id or auto-inferred fresh-context loops, e.g. Ralph overnight runs) with iterations, sessions, cost, flagged-call counts, and status (running / flagged / complete). |
| get_run_statusA | Status of one loop run: iterations so far, total cost and tokens, flagged calls, and whether the completion promise was seen (status=complete). Loop runners and agents can use this to decide whether to continue iterating. |
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/ShekharBhardwaj/AgenticLedger'
If you have feedback or need assistance with the MCP directory API, please join our Discord server