oracle_status
Health status of all 16 DORA OS oracles.
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
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only states 'health status', implying a read operation, but lacks details on auth requirements, response format, or any side effects. Minimal transparency.
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?
A single, clear sentence with no wasted words. It is perfectly concise and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with no parameters or output schema, but the description does not explain the return format or error conditions. It is minimally adequate but lacks completeness for an agent to fully understand expected output.
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?
There are zero parameters, so schema coverage is 100%. The description adds nothing about parameters, but none are needed. Baseline 4 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 returns the health status of all 16 DORA OS oracles. The verb (get/retrieve) is implied, and the resource (oracles) is specific. No sibling tool references oracles, so it is easily distinguished.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives like 'ping' or 'health_check'. The description provides no context for when to choose this tool over siblings.
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.