Skip to main content
Glama

BRAINIAC Config Hardening & Release Operations

Grade infrastructure config hardening

devops_config-hardening-grade

Grade a caller-supplied Dockerfile, Kubernetes YAML document, or Terraform JSON file for root execution, exposed ports, missing resource limits, and insecure defaults. Parsing stays in memory. The file is not applied, fetched, or stored. Price $0.04 USDC. POST /api/v1/devops/config-hardening-grade. 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": {
      "config": "<config>"
    },
    "name": "devops_config-hardening-grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 burden and does substantial work: it discloses that parsing is in-memory, that the file is not applied, fetched, or stored, and that unauthenticated payment failure returns 402 without execution. It omits rate limits and whether the operation is strictly read-only, but the safety-relevant behavior is well covered.

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?

Purpose is front-loaded in the first sentence, with scope, safety and billing details following in descending order of importance. Four tight sentences with no filler, though the commercial endpoint/price details are somewhat peripheral to an agent's decision to invoke.

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 one-parameter tool with no output schema and no annotations, the description should explain what a completed grading response looks like (findings shape, severity, counts). It says what is checked but nothing about the returned result, leaving a meaningful gap for an agent reasoning about downstream use.

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 0%, so the description must compensate, and it does: it establishes that the lone "config" string is the raw file content and enumerates the three accepted formats. It stops short of saying whether format is auto-detected or how malformed input is handled, so it is not fully complete.

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?

Uses a specific verb ("Grade") against a precisely enumerated resource set (Dockerfile, Kubernetes YAML, Terraform JSON) and names the exact checks performed (root execution, exposed ports, missing resource limits, insecure defaults). An agent can distinguish this static-hardening-grading tool from the blast-radius, release-readiness and rollback siblings purely from the text.

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 description makes clear what inputs are in scope and that the artifact is caller-supplied rather than fetched, which implies a pre-deployment/static-review context. However, it never states when an agent should pick this over the sibling audit tools, nor does it set exclusions (e.g., what to do with non-container/non-IaC inputs).

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