Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Audit OpenAPI 3.x security design

appsec-config_openapi-security-audit
Read-onlyIdempotent

OWASP API Top 10 style checks on an OpenAPI document. Price $0.04 USDC. POST /api/v1/appsec-config/openapi-security-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": {
      "spec": "<spec>"
    },
    "name": "appsec-config_openapi-security-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYesspec, string, length 0 to 5000000. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. 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, open-world. The description adds genuinely new behavioral context the annotations cannot express: the exact price ($0.04 USDC), the execution endpoint, and the crucial fact that an unpaid call returns x402 payment terms without running the audit. That payment/precondition disclosure is the main value add; return content details are left to 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.

Conciseness4/5

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

Three short sentences, with the purpose front-loaded ahead of the billing and endpoint details. Every clause carries information; the endpoint path is mildly redundant but aids routing diagnostics.

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?

An output schema exists so return values needn't be described, and annotations cover the safety profile. The description completes the picture with pricing and the unpaid-call behavior. Only the expected input format for 'spec' and failure modes on malformed documents are left unstated.

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 coverage is 100%, so the single 'spec' parameter is documented in the schema, giving a baseline of 3. The description adds nothing beyond that and notably does not clarify whether 'spec' is raw YAML/JSON text, a serialized object, or a reference to a stored document - a meaningful ambiguity for a 5MB string input.

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?

States a concrete check type and target: 'OWASP API Top 10 style checks on an OpenAPI document.' That clearly separates it from siblings like oauth-client-audit or jwt-inspect, which audit different artifacts. It does not name an alternative explicitly, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the payment mechanic but never says when to choose this audit over sibling audits (e.g. OAuth client audit, JWT inspect) or what preconditions make a document a good candidate. Only the billing behavior is spelled out, not usage conditions or exclusions.

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