agentsnap-mcp
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 |
|---|---|
| normalize_traceA | Coerce an arbitrary tool-call trace (an array of {name,args} entries or a partial Trace object) into the canonical agentsnap Trace shape. Returns the normalized trace plus a SHA-256 fingerprint hash computed over the canonical (key-sorted) JSON, so two runs can be byte-compared cheaply. |
| diff_tracesA | Diff two normalized agentsnap traces and surface meaningful differences. Returns same=true on a structural match, otherwise lists additions (paths only present in current), removals (paths only present in baseline), and changes (paths whose values differ). Use ignore_paths to drop noisy fields (e.g. ["fingerprint","tools[0].result_hash"]) before classification. |
| validate_snapshotA | Sanity-check a snapshot object against the agentsnap Trace schema. Verifies required fields (version, tools, fingerprint), tool-entry shape (name + args), and surfaces actionable issues. Returns valid=true on success, otherwise a list of human-readable issues. |
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 3 tools
Each tool targets a distinct operation: validating a snapshot against a schema, normalizing arbitrary traces into canonical form, and diffing two normalized traces. There is no overlap or confusion between these purposes.
All tool names follow a clear verb_noun pattern: validate_snapshot, normalize_trace, diff_traces. The naming is consistent, lowercase, and underscore-separated, making the toolkit predictable to navigate.
Three tools is on the low end but appropriate for a focused trace-processing utility. Each tool serves a distinct, essential role in the pipeline, and the count does not feel lacking for the stated scope.
The set covers the core workflow of validate → normalize → diff, which is a coherent and useful surface. Minor gaps exist, such as no explicit tool for fetching or writing traces, but these are outside the apparent purpose of the server.