Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Audit nginx configuration

appsec-config_nginx-config-audit
Read-onlyIdempotent

Find weak TLS, alias traversal, open proxy and missing headers. Price $0.03 USDC. POST /api/v1/appsec-config/nginx-config-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_nginx-config-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYescontent, string, length 0 to 2000000. 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.5/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 safety profile is covered. The description adds genuinely non-obvious operational context: a $0.03 USDC price, the x402 payment flow, and the critical fact that an unpaid call returns payment terms and does NOT execute. It does not describe finding severity or result shape, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what gets detected, then payment terms, then endpoint and unpaid-call semantics; every sentence carries information. The raw HTTP path is marginally redundant given the tool name but is cheap and useful for direct invocation.

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 single-input audit tool with rich annotations and an output schema, the definition covers the essentials, and the payment behavior disclosure is the key thing an agent could not otherwise know. The remaining gap is input format guidance for 'content', which is the one thing an agent must get right to call it successfully.

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?

There is one parameter, 'content', with 100% schema coverage, but the schema text is a generic placeholder ('content, string, length 0 to 2000000') that never says it is the raw nginx configuration text. The description lists the checks performed but never clarifies the expected input form (raw nginx.conf contents vs. a path or snippet), so it fails to add meaning where the schema is weakest.

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 names a concrete verb (find/audit) and enumerates the exact defect classes checked: weak TLS, alias traversal, open proxy, missing headers. It is clearly an nginx config audit, which separates it from the apache-config-audit sibling by resource, though it does not explicitly contrast with other appsec-config siblings.

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 only implied: an agent can infer you supply an nginx configuration and get findings back. There is no explicit statement of when to choose this over e.g. the apache audit, nor any prerequisite about what a valid config input looks like.

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