Skip to main content
Glama

Second Wind AI

deploy refuses to update export

cfn-export-in-use-update-plan
Read-onlyIdempotent

Send the deployed and target templates of the exporting stack and its importers. Returns which exports are blocked and why, the exact deploy order that clears the deadlock, the outputs to pin in the interim deployment, and generated CDK or CloudFormation pin code that reproduces each deployed export unchanged. Use when the error reads: Export cannot be deleted as it is in use by | Export cannot be updated as it is in use by | Cannot delete export as it is in use by . Covers: Same account and Region stacks linked by Outputs.Export and Fn::ImportValue, supplied as JSON templates. Does not cover CDK crossRegionReferences custom resources or Terraform consumers. Price: 2.00 USDC on Base via x402, charged only when the case is solved.

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": {
      "tool": "<tool>",
      "exporting_stack": "<exporting_stack>",
      "importing_stacks": "<importing_stacks>"
    },
    "name": "cfn-export-in-use-update-plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesWhat deploys these stacks.
regionNo
account_idNo
cdk_languageNoLanguage for generated CDK pin code. Default typescript.
error_messageNoThe deploy error text, if you have it.
exporting_stackYes
importing_stacksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: the 2.00 USDC x402 price on Base charged only when the case is solved, and the scope boundaries. It does not describe latency, size limits on templates, or failure modes, so it is good but not rich.

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 the return payload, then the trigger errors, then scope limits and price. The three near-identical error strings are somewhat repetitive but each is a distinct literal an agent may match against, so they earn their place. Slightly dense overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return-value burden and does so well by enumerating the four result components. For a nested, 7-parameter analysis tool the main gap is per-parameter guidance for the non-template fields, which the schema only partially covers.

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

Parameters3/5

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

Schema description coverage is only 43% across 7 parameters with nested objects, so the description should compensate more than it does. It explains the core payload ('deployed and target templates of the exporting stack and its importers') but says nothing about tool, region, account_id, cdk_language, or error_message semantics beyond what the schema already states. Baseline 3 for partial coverage.

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: it takes the deployed and target templates of an exporting stack plus its importers and returns blocked exports, the clearing deploy order, interim pin outputs, and generated pin code. That is clearly distinct from siblings like cfn-stuck-stack-recovery-plan or cdk-stack-dependency-cycle-fix.

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 exact trigger error strings ('Export <name> cannot be deleted as it is in use by <stack>', etc.), an explicit coverage statement (same-account/same-Region stacks linked by Outputs.Export and Fn::ImportValue, JSON templates), and explicit exclusions (CDK crossRegionReferences custom resources, Terraform consumers). An agent can decide to call or not call without inference.

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.

Resources