AgentSeal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTSEAL_API_KEY | Yes | Your AgentSeal API key for accessing the service |
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 |
|---|---|
| record_actionA | Record an agent action to the AgentSeal audit hash trail. Call this after every significant action (sending emails, modifying files, running queries, making API calls) to create a cryptographically sealed record of what happened and why. |
| query_actionsA | Look up previously recorded actions from the audit trail. Use this to check what actions have been taken, verify history, or recall past decisions. |
| verify_chainA | Verify the integrity of the audit trail hash chain. Each entry's SHA-256 hash includes the previous entry's hash — if any record was modified, the chain breaks and this will report where. |
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 has a clearly distinct purpose: record_action records, query_actions retrieves, verify_chain checks integrity. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (query_actions, record_action, verify_chain), making them predictable and easy to understand.
Three tools is an ideal scope for an audit trail server, covering the essential operations of recording, querying, and verifying without unnecessary bloat.
The tool surface fully covers the core lifecycle of an audit trail: recording actions, looking up history, and verifying chain integrity. No obvious gaps given the domain's immutability requirements.