Skip to main content
Glama

BRAINIAC Source Code Structure & Correctness Checks

Audit error propagation

code_error-propagation-audit

Find empty catches, swallowed promise rejections, logged-without-rethrow spans, and throw sites without local handlers in caller-supplied source. Pattern matches only; the code is not compiled or run. Price $0.04 USDC. POST /api/v1/code/error-propagation-audit. Unpaid calls return 402 and do 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": {
      "files": "<files>"
    },
    "name": "code_error-propagation-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the analytical fidelity ceiling (pattern matching, no compile/execution), the price ($0.04 USDC), the transport (POST endpoint), and failure semantics (402 on unpaid, no run). Remaining gaps are rate limits, per-language support, and any hint at what findings look like.

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 the detection targets, then fidelity, price, endpoint, and payment failure — a sensible information ordering with no filler sentences. The telegraphic fragment style is terse but every clause carries operational weight.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Coverage of cost, payment failure, and analysis fidelity is good for a paid audit endpoint. But with no output schema, the description gives no indication of the return shape (findings, locations, severity), and it omits the input size constraints an agent must respect — meaningful gaps for a tool with a nested parameter object.

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?

Schema description coverage is 0% for a single nested 'files' array containing path, source, and a language enum, plus minItems/maxItems and 100KB source caps. The description adds only 'caller-supplied source,' which implies source code input but explains nothing about the per-file object shape, the language enum, or the 200-file/100KB limits that would cause silent failures.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a concrete verb ('Find') with an enumerated set of detection targets: empty catches, swallowed promise rejections, logged-without-rethrow spans, and unhandled throw sites. That enumeration makes it unmistakable against siblings like code_concurrency-hazard-detect or code_maintainability-index without needing to name them.

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?

The phrase 'in caller-supplied source' plus 'Pattern matches only; the code is not compiled or run' implicitly tells the agent this is static, textual analysis and unsuitable when real semantic/dataflow results are needed. However, it never names an alternative tool or states explicit when-not conditions, so guidance is implied rather than stated.

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