recovery_status
Recovery readiness dashboard — how many systems are DR-ready.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
resilienceoracle
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only query but does not explicitly state the absence of side effects, what data is returned, or how 'DR-ready' is determined. This minimal disclosure leaves critical safety and behavior assumptions unstated.
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?
The description is a single concise sentence that front-loads the core purpose. It contains no redundant or filler content, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no parameters, the description should clarify the return format and meaning of 'DR-ready'. Phrases like 'how many systems' suggest a numeric count, but this is ambiguous. An agent would struggle to know what exact data to expect and how to interpret the result, so the description is insufficient for full autonomous invocation.
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?
The tool has zero parameters, and the schema description coverage is 100% (an empty schema). The description adds no parameter semantics, but the baseline for zero-parameter tools is 4, as there are no parameter ambiguities to clarify.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly indicates the tool provides a recovery readiness dashboard with a count of DR-ready systems. It is specific enough to distinguish it from siblings like 'health_check' by focusing on DR readiness, though it lacks an explicit verb such as 'get' or 'list'.
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?
The description provides no guidance on when to use this tool versus its alternatives. There is no mention of exclusions, prerequisites, or context, leaving the agent to infer usage solely from the name and sibling set.
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
Disambiguation5/5
Each tool targets a distinct function: registration, BIA setting, test logging, readiness status, specific compliance checks, and evidence collection. Even the check-type tools (bcm_gap_analysis, crisis_plan_check, rto_rpo_check) address clearly separated aspects.
Naming Consistency4/5
All names use lowercase with underscores, and most follow a verb_noun pattern (register_system, set_bia, test_register). A few noun-only names (evidence_bundle, scenario_library, recovery_status) deviate slightly, but the style remains consistent and readable.
Tool Count5/5
With 10 tools, the set is well-scoped for a BCM/DR compliance server. Each tool serves a necessary part of the workflow—system registration, BIA, testing, checks, and evidence—without redundancy.
Completeness4/5
The server covers the core BCM lifecycle: register systems, set BIA, run tests, check compliance, and bundle evidence. Minor gaps exist (e.g., no update/delete for systems or BIA), but these are workaround-able using set_bia and are not critical for the stated purpose.