Skip to main content
Glama

dr_strategy

Read-onlyIdempotent

Compare disaster recovery tiers against RTO, RPO, and data constraints to identify feasible options and required capabilities; results are guidance, not a guarantee.

Instructions

Compare disaster recovery tiers (backup-and-restore, pilot light, warm standby, active-active) against RTO, RPO and data constraints; returns feasible tiers and required capabilities, not a guarantee.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workload": "<workload>",
      "rtoMinutes": "<rtoMinutes>",
      "rpoMinutes": "<rpoMinutes>"
    },
    "name": "dr_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataGBNo
workloadYes
rpoMinutesYes
rtoMinutesYes
statefulComponentsNo
regulatoryResidencyNo
replicationBandwidthMbpsNo

Output Schema

NameRequiredDescriptionDefault
kindNo
tiersNo
checksNo
sourcesNo
workloadNo
nextToolsNo
validatedNo
limitationNo
objectivesNo
initialFullCopyHoursNo
recommendedStartingPointNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / required
      Previous value: -[
      -  "workload",
      -  "rtoMinutes",
      -  "rpoMinutes",
      -  "dataGB",
      -  "statefulComponents"
      -]New value: +[
      +  "workload",
      +  "rtoMinutes",
      +  "rpoMinutes"
      +]
  2. First observedv0.4.1

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does so meaningfully by framing the result as an advisory feasibility assessment ('returns feasible tiers and required capabilities, not a guarantee'), warning the agent not to treat output as authoritative. It does not discuss the cost or limits of the analysis, which keeps it below 5.

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 dense sentence, front-loaded with the comparison and followed by the return-shape caveat; every clause carries information and there is no filler.

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?

Because an output schema exists, the description need not explain return values, and the annotations cover safety. However, for a 7-parameter analytical tool with zero schema descriptions, the omitted inputs (statefulComponents, regulatoryResidency, replicationBandwidthMbps) materially affect which tiers are feasible, so the definition is only adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description must carry the semantics, but it only gestures at RTO, RPO, and 'data constraints' (loosely rtoMinutes, rpoMinutes, dataGB). Four parameters — workload, statefulComponents, regulatoryResidency, replicationBandwidthMbps — get no explanation at all, and their purpose (e.g., residency restricting region choice, bandwidth constraining replication tier) is not inferable from the description.

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?

Uses a specific verb ('Compare') on a named resource ('disaster recovery tiers') and enumerates the four tiers, plus names the criteria (RTO, RPO, data constraints) and the output (feasible tiers and required capabilities). This is clearly separable from adjacent siblings such as service_compare or architecture_pattern.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrasing: call this when evaluating which DR tier fits a workload's RTO/RPO envelope. There is no explicit when-not guidance, no named alternative tool, and no statement of prerequisites (e.g., that workload must be characterized first).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.