Skip to main content
Glama

BRAINIAC Config Hardening & Release Operations

Check rollback feasibility

devops_rollback-feasibility-check

Evaluate whether a proposed deployment can be rolled back using supplied versions, migration reversibility, compatibility constraints, and recovery procedures. No deployment platform is queried. Price $0.04 USDC. POST /api/v1/devops/rollback-feasibility-check. 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": {
      "versions": "<versions>"
    },
    "name": "devops_rollback-feasibility-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionsYes
migrationsNo
compatibilityNo
max_rto_minutesNo
recovery_proceduresNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose important traits: no deployment platform is queried, the call costs $0.04 USDC, and unpaid calls return 402 without running. It does not describe the response shape or whether results are stored, but the cost, payment gate, and no-external-query behavior are substantial disclosures.

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 front-loaded with the purpose and then adds only necessary operational facts: no platform query, price, endpoint, and 402 behavior. There is no filler or repetition.

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?

The tool has five parameters with nested objects and no output schema. The description covers purpose, cost, and payment behavior, but it does not explain what the feasibility result contains, which is a meaningful gap when no output schema exists.

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%, so the description must compensate for five parameters. It names four input domains (versions, migrations, compatibility, recovery procedures) but omits max_rto_minutes entirely and does not explain required fields, nested structures, or the meaning of fields like reversible and compatible_with_rollback.

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?

The description gives a specific verb and resource: 'Evaluate whether a proposed deployment can be rolled back.' It also names the evidence used (versions, migration reversibility, compatibility constraints, recovery procedures), making the tool clearly distinct from sibling audit/grade/blast-radius tools.

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 'proposed deployment,' suggesting a pre-deployment check, but the description never states when to use this tool versus alternatives or when not to use it. No siblings or exclusion conditions are named.

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