Skip to main content
Glama

BRAINIAC Payload Safety & Architecture Control Checks

Find security control coverage gaps

security_security-control-coverage-gap
Read-onlyIdempotent

Compare supplied security requirements with declared controls and evidence. Report requirements with no matching control or with matching controls that lack evidence. No cloud account is queried. Price $0.04 USDC. POST /api/v1/security/security-control-coverage-gap. An unpaid call returns the x402 payment terms and does 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": {
      "requirements": "<requirements>",
      "controls": "<controls>"
    },
    "name": "security_security-control-coverage-gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
zonesNozones, array. Optional.
controlsYescontrols, array. Required.
evidenceNoevidence, array. Optional.
componentsNocomponents, array. Optional.
requirementsYesrequirements, array. Required.

Output Schema

NameRequiredDescriptionDefault
summaryNosummary. Object.
findingsNofindings. Array.
explanationsNoexplanations. Array.

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?

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds meaningful non-annotation behavior: no cloud account is queried, a USDC price, the POST endpoint, and that unpaid calls return x402 payment terms without running. It does not cover rate limits or detailed return values, but an output schema exists.

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 short and front-loads purpose, then reporting logic, then important execution and payment constraints. Every sentence carries operational value, and nothing is redundant.

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?

For a comparison tool with rich schema coverage and an output schema, the description covers purpose, gap criteria, cloud-access behavior, and payment gating. It omits explicit sibling routing and a little operational context, but is otherwise complete enough to invoke correctly.

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 100%, so the schema already documents all five parameters, including nested fields and enums. The description only maps conceptually to supplied requirements, controls, and evidence, adding little parameter-level syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 precise comparison and reporting action over requirements, controls, and evidence, and names the exact gap categories: no matching control, or matching controls lacking evidence. The coverage-gap focus is clearly distinguishable from anomaly scoring, data-flow auditing, or trust-boundary detection.

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 implies when to use it: when supplied requirements, controls, and optional evidence need to be checked for coverage gaps. It does not explicitly name alternatives or state when not to use it, so guidance is adequate but limited.

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