Skip to main content
Glama

BRAINIAC Config Hardening & Release Operations

Calculate deployment blast radius

devops_deployment-blast-radius

Walk a caller-supplied service dependency graph from proposed changes and list upstream and downstream services that may be affected. No CI/CD system is contacted. Price $0.04 USDC. POST /api/v1/devops/deployment-blast-radius. Unpaid calls return 402 and do not run.

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": {
      "services": "<services>",
      "dependencies": "<dependencies>",
      "changes": "<changes>"
    },
    "name": "devops_deployment-blast-radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
servicesYes
directionNo
dependenciesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses that no external CI/CD system is contacted (no side effects), that the call is paid at $0.04 USDC, the POST endpoint, and that unpaid calls return 402 without running. That covers side effects, auth/payment, and failure mode. It stops short of describing result shape or ordering of the affected services.

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?

The definition is compact and front-loads the operation before the practical constraints (no CI/CD, price, endpoint, 402 behavior). Every sentence is functional, though the pricing and endpoint details are slightly operational rather than semantic.

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?

For a four-parameter tool with nested arrays, no annotations, and no output schema, the description supplies purpose, side-effect profile, and payment behavior but leaves the parameter semantics and the structure of the returned affected-services list unexplained. Adequate to select the tool, thin for invoking it correctly with well-formed inputs.

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 0%, so the description must carry parameter meaning, and it only partially does: it names the dependency graph, proposed changes, and upstream/downstream direction conceptually. It adds nothing about the enum values (change_kind, tier, dependency kind), required versus optional fields, or the array size limits in the schema.

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?

States a specific verb and resource: walk a caller-supplied service dependency graph from proposed changes and list upstream and downstream affected services. It goes beyond the title by naming the mechanism (dependency graph, not live discovery). It does not explicitly contrast itself with the sibling audit tools, but the operation is unambiguous.

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?

The phrase 'from proposed changes' implies the use case of pre-deployment impact assessment, and 'No CI/CD system is contacted' clarifies the operating context. However, it never states when to prefer this over the sibling release-readiness or rollback-feasibility tools, and offers no explicit exclusions or prerequisites beyond payment.

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