workflow_library
List all available predefined workflows with descriptions and step counts.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
conductor
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but the description accurately conveys the read-only nature and output content (descriptions and step counts) without contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with the core purpose, no superfluous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter listing tool, the description completely covers what the tool does and what it returns, given no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; schema has 100% coverage with an empty object, and the description adds no parameter details, which is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists all available predefined workflows with descriptions and step counts, distinguishing it from execution-focused siblings like run_workflow.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for browsing/discovering workflows rather than executing them, but does not explicitly state when to use versus alternatives like run_workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.2/5.0
Disambiguation4/5
Most tools have distinct purposes, but health_check, oracle_status, and readiness_dashboard overlap in providing health/status information, which could cause confusion for an agent. The descriptions help differentiate their scope (e.g., oracle_status for 16 DORA oracles, readiness_dashboard for 23 oracles + tool count).
Naming Consistency5/5
All tool names use consistent snake_case, lowercase format, and follow a predictable verb_noun or noun_noun pattern (e.g., board_briefing, react_to_event, onboard_entity). No mixed conventions or irregular naming.
Tool Count5/5
16 tools is appropriate for a DORA compliance and monitoring server covering onboarding, health checks, assessments, gap analysis, remediation, event reactions, and workflows. Each tool has a defined role, and the count is well-scoped for the domain.
Completeness4/5
The tool set covers core compliance workflows: onboarding, assessments, health status, gap analysis, remediation planning, event reaction, and syncing. Minor gaps exist, such as lacking a tool to manually update individual compliance items, but the workflow and sync tools compensate. Overall, the coverage is strong.