AgentTakt
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 |
|---|---|
| request_approvalA | Submit a task execution plan for human review in the AgentTakt editor. Blocks until the human approves or rejects the plan in the TUI. Returns {"status": "approved" | "rejected", "plan": , "reason": <str | null>}. The returned plan may differ from the submitted one (the human can edit nodes, edges and parameters) — always execute the returned plan. Args: plan: Plan JSON with graph_id, nodes[] and edges[] (must be a DAG). summary: One-line description shown in the editor header. |
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 confusion or overlap. The tool has a clear, single purpose.
With only one tool, naming consistency is trivially satisfied. The name 'request_approval' clearly follows a verb_noun pattern and is unambiguous.
A single tool is too few for a server that might reasonably support additional operations such as querying approval status or managing plans. The minimal surface feels thin for a general-purpose agent toolkit.
The tool covers the full submit-and-wait-for-approval lifecycle, but there are minor gaps like cancellation or historical querying. For its stated purpose, the core workflow is complete.