Runbook
OfficialServer 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_runbookD | – |
| delete_runbookD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| get_runbook_as_prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| runbooks://runbooks |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: create_runbook for creating a runbook and delete_runbook for deleting one, with no overlap in functionality. This minimal set avoids any ambiguity, as each tool targets a specific, opposite action on the same resource.
Both tools follow a consistent verb_noun pattern (create_runbook and delete_runbook), using snake_case and clear action verbs. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With only two tools, the server feels too thin for a runbook management domain, as it lacks essential operations like listing, retrieving, or updating runbooks. While the tools are well-defined, the count is insufficient for typical CRUD workflows, limiting agent capabilities.
The tool set is severely incomplete for runbook management, missing key operations such as get_runbook, list_runbooks, and update_runbook. This creates significant gaps that will cause agent failures, as users cannot retrieve or modify existing runbooks, leading to dead ends in workflows.