agent-config
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 |
|---|---|
| get_setup_statusC | Query setup and configuration readiness status for the current host and workspace. |
| inspect_hostA | Inspect host runtime capabilities, available models, supported effort values, and execution topology. |
| get_profileB | Retrieve the stored, user-confirmed Agent Config profile for the specified host and workspace. |
| save_profileB | Atomically validate and save a user-confirmed Agent Config profile. |
| preview_configurationA | Generate a configuration preview (diff and mutation targets) before applying any changes. |
| apply_configurationA | Apply a previously previewed configuration using a valid preview ID. |
| validate_configurationB | Verify that actual host configuration matches expected configuration after apply. |
| reset_profileA | Safely clear and remove the host-scoped profile for the specified workspace. |
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 8 tools
Most tools map cleanly to distinct actions (profile CRUD vs configuration preview/apply/validate), but get_setup_status and validate_configuration both touch configuration state, which could cause minor confusion. Overall, descriptions are clear enough to guide correct selection.
All tool names follow a consistent verb_noun snake_case pattern with specific verbs like get, save, reset, preview, apply, validate, and inspect. The naming style is uniform and predictable.
Eight tools is well-scoped for an agent configuration server. Each tool serves a clear purpose without redundancy, covering status discovery, host inspection, profile management, and configuration lifecycle actions.
The tool set supports the full configuration workflow: check readiness, inspect the host, retrieve/save/reset profiles, preview changes, apply changes, and validate results. No critical operations appear to be missing for the stated purpose.