FRD Orchestrator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRD_ORCH_LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | INFO |
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 |
|---|---|
| get_frdB | Returns the content of an FRD by id. 00 -> FRD-00-master-orchestration.md 01 -> FRD-01-boilerplate-core-products.md ... |
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 possibility of ambiguity or overlap between tools. The single tool 'get_frd' has a clear and distinct purpose of retrieving FRD content by ID.
The naming is trivially consistent as there is only one tool. The tool name 'get_frd' follows a clear verb_noun pattern (get + FRD), which would be appropriate if more tools were added.
A single tool is too few for a server named 'FRD Orchestrator', which implies orchestration capabilities beyond simple retrieval. The scope suggests operations like create, update, delete, or manage FRDs, but only a read operation is provided.
The tool surface is severely incomplete for an orchestrator. It only supports retrieving FRDs by ID, lacking essential operations such as creating, updating, deleting, listing, or searching FRDs. This will cause significant agent failures in orchestration tasks.