Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Audit GitLab CI configuration

appsec-config_gitlab-ci-audit
Read-onlyIdempotent

Flag unpinned images, remote includes, secrets and dind risks. Price $0.03 USDC. POST /api/v1/appsec-config/gitlab-ci-audit. 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": {
      "content": "<content>"
    },
    "name": "appsec-config_gitlab-ci-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYescontent, string, length 0 to 2000000. Required.
requireDigestNorequireDigest, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. Array.
unresolvedIncludesNounresolvedIncludes. Array.

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?

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the description's added value is the cost ($0.03 USDC), the transport endpoint, and the important failure mode that an unpaid call returns x402 payment terms without executing. That is meaningful operational context an agent cannot get from the annotations; return-value detail is covered by the output schema.

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?

Three sentences, risk surface first, then cost, then the payment failure mode — each sentence contributes distinct information with no filler or repetition of the title.

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?

With only two parameters, full schema coverage, an output schema, and annotations covering safety, the description supplies what remains: what it checks, what it costs, and what happens when payment is missing. The one gap is that it never clarifies the expected form of the 'content' payload, which is the only required input.

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 both parameters (content, requireDigest) are documented in structured data and the baseline is 3. The description adds no meaning about what 'content' should contain (raw YAML vs. a path or ref) or when to set requireDigest, leaving that entirely to 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?

The description gives a specific verb ('Flag') plus the exact risk classes it detects (unpinned images, remote includes, secrets, dind) and scopes them to GitLab CI, which separates it from the github-actions/nginx/apache audit siblings by name and subject. It stops short of an explicit contrast statement, but an agent can identify the target artifact unambiguously.

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: point it at a GitLab CI configuration to get findings. There is no explicit statement of when to prefer this over a sibling audit, no prerequisite note about needing a paid/x402-enabled client beyond the payment caveat, and no exclusions. Adequate but inferential.

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