agenteng
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTENG_MODEL | No | Operator-selected model required when enabling standard or RLM engines. | |
| AGENTENG_ENABLE_RLM | No | Set to 1 to enable the RLM model engine. Disabled by default. | |
| AGENTENG_PUBLIC_URL | No | Set to your HTTPS origin for self-hosting. Used to configure allowed origins. | |
| AGENTENG_MODEL_API_KEY | No | Provider API key required when enabling standard or RLM engines. | |
| AGENTENG_MODEL_BASE_URL | No | Base URL for an OpenAI-compatible provider. Optional. | |
| AGENTENG_OPERATOR_TOKEN | No | Operator bearer credential required when enabling standard or RLM engines. | |
| AGENTENG_ENABLE_STANDARD | No | Set to 1 to enable the standard model engine. Disabled by default. |
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 |
|---|---|
| agentengC | Discover AgentEng conferences in London and San Francisco, browse agent-engineering tools across twelve disciplines, query public facts and prepare proposals for Agent Engineering HQ. |
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 selecting the wrong tool from a set. However, the tool's description bundles multiple distinct functions (discovering conferences, browsing tools, querying facts, preparing proposals), making its scope broad and less clearly bounded.
A single tool name cannot demonstrate a consistent pattern across a set. The name 'agenteng' matches the server but is a bare noun rather than a predictable verb_noun action, which is readable but not ideal for an MCP tool.
The server's apparent purpose spans multiple operations across conferences, tools, facts, and proposals. A single catch-all tool is too few to expose those operations clearly, forcing agents to rely on one broad interface.
The domain implies distinct lifecycle actions such as discovering, browsing, querying, and preparing proposals. The surface provides no separate operations for these tasks, leaving severe gaps for agents attempting specific workflows.