Skip to main content
Glama

BRAINIAC Config Hardening & Release Operations

Audit release readiness

devops_release-readiness-audit

Check whether a release meets supplied operational requirements: prerequisites, monitoring coverage, rollback plans, and unresolved blockers. Returns concrete gaps rather than a generic risk score. Price $0.04 USDC. POST /api/v1/devops/release-readiness-audit. 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": {
      "release_id": "<release_id>",
      "services": "<services>"
    },
    "name": "devops_release-readiness-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockersNo
servicesYes
monitoringNo
release_idYes
prerequisitesNo
rollback_plansNo
require_monitoring_per_serviceNo
require_rollback_plan_per_serviceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing the paid-access model: $0.04 USDC, POST /api/v1/devops/release-readiness-audit, and unpaid calls returning 402 without executing. That is real behavioral context an agent needs. It does not, however, state that the operation is read-only/non-mutating, whether supplied data is persisted, or whether results are deterministic, which matters for an audit tool.

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 purpose, then the output character, then the payment mechanics in a compact sequence. Every sentence carries content; no filler or duplicated restatement of the title.

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

Completeness2/5

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

For an 8-parameter, nested-schema, no-annotation, no-output-schema tool, the description covers purpose and billing but leaves the parameter contract almost entirely unexplained, including two boolean switches that alter results. An agent can understand what the tool is for but not how to construct a correct call from the description alone.

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 8 parameters, several of them nested arrays with required sub-fields. The description's category list loosely maps to the prerequisites, monitoring, blockers, and rollback_plans arrays, but says nothing about release_id, services, or the require_monitoring_per_service and require_rollback_plan_per_service flags, which materially change the audit's verdict logic.

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?

Uses a specific verb and resource ('Check whether a release meets supplied operational requirements') and enumerates the four audited dimensions: prerequisites, monitoring coverage, rollback plans, and unresolved blockers. It also differentiates its output style ('concrete gaps rather than a generic risk score'), which separates it somewhat from sibling grading tools, though no sibling is named explicitly.

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 enumeration of requirement categories and by the contrast with a 'generic risk score', suggesting it is used when a definitive gap list is wanted. However, there is no explicit when-to-use versus devops_rollback-feasibility-check or devops_config-hardening-grade guidance, and no stated preconditions for what must be supplied.

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