Skip to main content
Glama

Crisis Planner

crisis_planner
Read-only

Generates crisis playbooks with response team roles and notification steps for operational crises, tailored to company, industry, customer base, data sensitivity, and compliance needs.

Instructions

Helps you decide who does what when a crisis hits: it takes your company, industry, customer base and data sensitivity, and returns crisis playbooks with a response team and notification steps for each crisis. Name the crises you know of to get those playbooks; without them it uses a default set of common crises for your sector, not ranked by likelihood. Each compliance item you list is used in the notification steps. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of retention_playbook when you need response roles and notification steps for operational crises.

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": {
      "company": "<company>",
      "industry": "<industry>",
      "customer_base": "<customer_base>",
      "data_sensitivity": "<data_sensitivity>"
    },
    "name": "crisis_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany name. Format is text. For example, "invoice review service".
industryYesIndustry affects which crises to prioritize. Format is text using one of the listed labels. For example, "fintech".
your_sectorNoOptional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech".
company_sizeNoAffects response team structure. Format is text using one of the listed labels. For example, "startup_under_50".
customer_baseYesCustomer type affects communication approach. Format is text using one of the listed labels. For example, "b2b_enterprise".
business_modelNoOptional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, "saas".
data_sensitivityYesData sensitivity affects security protocols. Format is text using one of the listed labels. For example, "high_pii_financial".
potential_crisesNoOptional: crisis types to plan for, comma-separated. If not provided, the tool uses a default set of common crises for your sector (not ranked by likelihood). Options: data_breach, service_outage, sla_breach, regulatory_action, fraud_incident, ai_wrong_action, pr_incident, executive_departure, security_vulnerability, customer_data_exposure, product_safety. Format is text. For example, "service outage during month-end close".
compliance_requirementsNoOptional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps. Format is text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.2.25
    • addedInput schema / properties / business_model
      Added value: +{
      +  "description": "Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, \"saas\".",
      +  "enum": [
      +    "saas",
      +    "services",
      +    "connectivity",
      +    "transactions",
      +    "marketplace",
      +    "hardware_software",
      +    "investment"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / company / description
      Previous value: -"Company name"New value: +"Company name. Format is text. For example, \"invoice review service\"."
    • addedInput schema / properties / company_size
      Added value: +{
      +  "description": "Affects response team structure. Format is text using one of the listed labels. For example, \"startup_under_50\".",
      +  "enum": [
      +    "startup_under_50",
      +    "scaleup_50_200",
      +    "midsize_200_1000",
      +    "enterprise_1000_plus"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / compliance_requirements
      Added value: +{
      +  "description": "Optional: Relevant compliance, comma-separated (for example ISO 27001, SOC 2, GDPR). Each item is named in the notification steps. Format is text.",
      +  "type": "string"
      +}
    • addedInput schema / properties / customer_base
      Added value: +{
      +  "description": "Customer type affects communication approach. Format is text using one of the listed labels. For example, \"b2b_enterprise\".",
      +  "enum": [
      +    "b2b_enterprise",
      +    "b2b_smb",
      +    "b2c_consumer",
      +    "mixed"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / data_sensitivity
      Added value: +{
      +  "description": "Data sensitivity affects security protocols. Format is text using one of the listed labels. For example, \"high_pii_financial\".",
      +  "enum": [
      +    "high_pii_financial",
      +    "medium_business_data",
      +    "low_general"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / industry / description
      Previous value: -"Industry/sector"New value: +"Industry affects which crises to prioritize. Format is text using one of the listed labels. For example, \"fintech\"."
    • addedInput schema / properties / industry / enum
      Added value: +[
      +  "fintech",
      +  "saas",
      +  "logistics_tech",
      +  "vertical_saas",
      +  "ai_native",
      +  "ites",
      +  "telecom",
      +  "software",
      +  "cybersecurity",
      +  "ecommerce",
      +  "enterprise",
      +  "consumer",
      +  "other"
      +]
    • changedInput schema / properties / potential_crises / description
      Previous value: -"Types: product issues, security, PR, operational"New value: +"Optional: crisis types to plan for, comma-separated. If not provided, the tool uses a default set of common crises for your sector (not ranked by likelihood). Options: data_breach, service_outage, sla_breach, regulatory_action, fraud_incident, ai_wrong_action, pr_incident, executive_departure, security_vulnerability, customer_data_exposure, product_safety. Format is text. For example, \"service outage during month-end close\"."
    • removedInput schema / properties / spokesperson
      Removed value: -{
      -  "description": "Who speaks for company",
      -  "type": "string"
      -}
    • removedInput schema / properties / stakeholders
      Removed value: -{
      -  "description": "Key stakeholders",
      -  "type": "string"
      -}
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "company",
      -  "industry",
      -  "potential_crises"
      -]New value: +[
      +  "company",
      +  "industry",
      +  "customer_base",
      +  "data_sensitivity"
      +]
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only and non-destructive behavior, but the description adds substantive context beyond them: no sign-in required, no storage of inputs or outputs, hosted usage metadata recorded, and that missing required fields or invalid values return an error naming what to supply. That is exactly the behavioral disclosure an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and return value, then behavior, then the sibling exclusion. It is a dense single block though, and the privacy/error sentences could be tightened, but no sentence is genuinely wasted.

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 nine-parameter, no-output-schema tool, the description covers inputs, defaults, error handling, privacy/side effects, and the sibling alternative. Nothing an agent needs to select and invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that compliance_requirements items are each named in the notification steps and that omitted potential_crises falls back to a sector default set rather than being required. Minor gain only, since most parameter semantics are already fully documented in the schema.

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?

States a specific verb and resource (returns crisis playbooks with a response team and notification steps) and explicitly names what it takes as input. It also distinguishes itself from the sibling retention_playbook by scoping to operational crises needing response roles and notification steps.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: name the crises you know of to get those playbooks, otherwise a sector default is used, and it directly names retention_playbook as the alternative with the condition that selects this tool instead. It also flags that defaults are not ranked by likelihood, which the agent needs to interpret output.

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