titmas-agent-action-gate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TITMAS_ACTION_GATE_DEMO_MODE | Yes | If 'true', enables demo mode. Example: 'true'. | |
| TITMAS_ACTION_GATE_STATE_DIR | Yes | Directory for storing action gate state (append-only store). Example: 'artifacts/runtime/mcp'. | |
| TITMAS_ACTION_GATE_CALLER_TOKEN | Yes | Token used by the caller agent to authenticate with the action gate. | |
| TITMAS_ACTION_GATE_MCP_TRANSPORT | Yes | Transport for MCP server. Example: 'stdio'. | |
| TITMAS_ACTION_GATE_APPROVER_TOKEN | Yes | Token used by the approver role to authenticate for approvals. |
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 |
|---|---|
| submit_action_requestC | Validate and append one normalized action request; grants no authority. |
| attach_evidenceA | Attach an immutable in-scope evidence profile reference; does not verify or authorize it. |
| verify_evidenceC | Invoke pinned agent-evidence 0.6.0 and retain its structured receipt. |
| evaluate_action_gateC | Compute deterministic ALLOW, BLOCK, or REQUIRE_APPROVAL from retained versioned inputs. |
| record_human_approvalB | Create and append a scoped signed human approval, denial, or revocation input. |
| get_action_stateA | Read append-only action state and integrity results; performs no mutation. |
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 6 tools
Each tool targets a distinct phase of the action gate workflow: submitting a request, attaching evidence, verifying evidence, evaluating the gate, reading state, and recording human approval. There is no overlap in purpose or ambiguity about which tool to use.
All tool names follow a consistent verb_noun pattern with clear, domain-specific verbs (submit, attach, verify, evaluate, get, record). The naming is uniform, predictable, and free of mixed styles or vague terms.
With six tools, the server is well-scoped for an action gate domain. Each tool maps to a core step in the process, avoiding both bloat and a thin surface.
The tool set covers the complete action gate lifecycle: request intake, evidence attachment and verification, gate evaluation, human approval input, and state inspection. Given the append-only and integrity-focused design, there are no obvious missing operations.