agy-foreman
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agy_statusB | Get status of delegation, cooldown, active and queued jobs |
| agy_startC | Start an implement or explore delegation job |
| agy_getC | Get job record and diff by job ID |
| agy_actC | Act on a job or delegation state |
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 4 tools
Each tool targets a distinct aspect of delegation: global status, starting a job, retrieving a job by ID, and acting on existing jobs. The main weakness is agy_act, which is broad and could overlap with agy_start or agy_get in edge cases.
All tools share the consistent agy_ prefix followed by a short action word. The only minor deviation is agy_status using a noun rather than a verb, but the pattern remains highly predictable.
Four tools is a lean, well-scoped surface for a delegation foreman, with no obvious filler or redundant entries. Each tool appears to earn its place in the lifecycle.
The set covers job creation, global monitoring, per-job retrieval with diffs, and actions on jobs or delegation state. Cancellation, retry, or waiting operations are not explicit but are likely handled by agy_act, leaving only minor gaps.