agent-observability
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runA | Run the agent-trace CLI with the given subcommand/args; --json is appended automatically so the result is machine-readable JSON. Only these subcommands support --json today: list, replay, inspect, diff, run. Real Run the agent-trace CLI (agent-observability-trace-cli). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of overlap or confusion between tools. The single 'run' tool clearly delegates to CLI subcommands, making its purpose unambiguous.
With only one tool, naming consistency is trivially maintained. The name 'run' is a simple verb that matches its role as an executor, though it lacks a noun prefix that might better indicate the subject.
A single tool for wrapping an entire CLI is borderline. It feels thin for a server that could expose multiple distinct operations, but it is also a pragmatic design if the CLI is the core interface. The count is acceptable but not expansive.
The single 'run' tool provides access to all JSON-supporting subcommands (list, replay, inspect, diff, run), covering the main workflows of the agent-observability domain. Minor gaps exist, such as no dedicated help or non-JSON commands, but these are not critical for typical usage.