Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Evaluate a password policy vs NIST

appsec-config_password-policy-evaluate
Read-onlyIdempotent

Check policy fields and optional samples against NIST SP 800-63B-4. Price $0.02 USDC. POST /api/v1/appsec-config/password-policy-evaluate. 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": {
      "policy": "<policy>"
    },
    "name": "appsec-config_password-policy-evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYespolicy, object. Required.
samplesNosamples, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourceNosource. String.
samplesNosamples. Array.
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, and the description adds genuinely non-obvious context: the $0.02 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not execute. That payment gating is exactly the kind of behavior an agent cannot infer from annotations or 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?

Four short sentences with no filler: purpose first, then price, endpoint, and payment behavior. Every sentence carries information an agent would otherwise have to discover by failing a call.

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 a full input schema, an output schema, and annotations, the description needs only to add the non-structured facts, and it does: cost, transport, and the payment-gated failure mode. It could say slightly more about what the evaluation covers (e.g. which policy dimensions are scored), but nothing essential to correct invocation is missing.

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% and every nested policy field is documented, so the schema carries the parameter burden. The description adds only that samples are optional test inputs alongside policy fields, which is a minor semantic addition, so the baseline of 3 applies.

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 states a specific verb and resource ('Check policy fields and optional samples') plus the exact standard applied (NIST SP 800-63B-4), which makes it unambiguous what the tool returns an assessment of. It does not explicitly name a sibling or state why it differs from the other appsec audit tools, so it falls just short of the top band.

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?

There is no when-to-use guidance, no prerequisites, and no alternatives named. The closest thing to guidance is the mention that an unpaid call returns payment terms rather than results, which is a failure-mode note rather than a usage rule.

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