Agent Action Preflight v1
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AAP_CONFIG | No | Path to a sample configuration file. | |
| AAP_RECEIPTS_DIR | No | Directory where receipts are stored. | |
| AAP_STORAGE_ROOT | No | Local storage root for notes. |
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 |
|---|---|
| execute_preflighted_noteC | Preflight a concrete local note action, then write it only when the present configuration forms that transition. |
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
With only one tool, there is no risk of overlapping purposes or misselection. The single tool's responsibility is clearly unique by default.
The sole tool name follows a verb_object pattern (execute_preflighted_note) and there are no mixed conventions to penalize.
A one-tool server feels thin for an 'Agent Action Preflight' scope, though the tool itself is non-trivial and narrowly focused.
Only an execute-with-preflight operation is exposed; agents have no way to inspect current configuration, separate preflight from execution, or recover from failed writes, creating significant gaps.