Skip to main content
Glama

BRAINIAC Payload Safety & Architecture Control Checks

Score payload anomaly and input safety

security_payload-anomaly-score
Read-onlyIdempotent

Score a caller-supplied JSON value or text string for nesting depth, mixed types, injection-shaped text, and size inflation. Matching is local and deterministic. The payload is not executed, fetched, or stored. Price $0.04 USDC. POST /api/v1/security/payload-anomaly-score. 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": {
      "payload": "<payload>"
    },
    "name": "security_payload-anomaly-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYespayload, value. Required.

Output Schema

NameRequiredDescriptionDefault
audit_receiptNoaudit_receipt. String.
risk_breakdownNorisk_breakdown. Object.
anomalies_detectedNoanomalies_detected. Array.
overall_safety_scoreNooverall_safety_score. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the costly-to-assume behaviors: matching is local and deterministic, and the payload is not executed, fetched, or stored. It also documents the commercial and transport layer — $0.04 USDC, POST /api/v1/security/payload-anomaly-score — and the unpaid-call short-circuit, none of which are derivable 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, front-loaded sentences: what is scored, how matching behaves, what is not done with the payload, then the cost and payment mechanics. Every sentence carries information an agent needs before calling; nothing is padded or repeated from the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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-value detail is not required in the description. For a one-parameter, read-only scorer, the description covers purpose, deterministic behavior, data-handling guarantees, pricing, and the unpaid-call path — everything needed to invoke it correctly the first time.

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% for the single `payload` parameter, so the schema already carries the type union and limits. The description's mention of 'JSON value or text string' restates the anyOf rather than adding format, encoding, or size-ceiling guidance (e.g., the 200k character / 5000 element caps) beyond the schema. Baseline 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 names a specific verb and resource ('Score a caller-supplied JSON value or text string') and enumerates the four dimensions measured: nesting depth, mixed types, injection-shaped text, and size inflation. It is unambiguous about what the tool produces, though it never names or contrasts with the sibling audit tools (coverage-gap, data-flow, trust-boundary), leaving differentiation to inference.

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

Usage Guidelines4/5

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

Usage context is clear: the tool operates on a caller-supplied payload and is meant for input-safety screening. It also states the payment precondition ('An unpaid call returns the x402 payment terms and does not run'), which tells the agent what to expect on first invocation. It stops short of explicit when-to-use/when-not-to-use routing against the sibling audit tools.

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