Skip to main content
Glama

BRAINIAC Source Code Structure & Correctness Checks

Analyze change coupling

code_change-coupling-analyze

Identify files outside a proposed change set that are coupled through supplied module edges, import paths, or historical co-change sets. The source is not compiled or executed. Price $0.04 USDC. POST /api/v1/code/change-coupling-analyze. 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>",
      "proposed_paths": "<proposed_paths>"
    },
    "name": "code_change-coupling-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
change_setsNo
module_edgesNo
proposed_pathsYes

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?

With no annotations, the description carries the full burden and does meaningful work: it discloses that source is not compiled or executed (a safety-relevant fact), the price ($0.04 USDC), the payment gate (402 on unpaid calls, nothing runs), and the transport endpoint. It stops short of describing output shape or determinism.

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?

Four short sentences, purpose front-loaded, and each sentence carries operational information (scope, safety, price, payment behavior). The endpoint string is the only marginal filler, and it is still useful for a paid HTTP tool.

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?

For a tool accepting up to 200 source files and 5000 module edges with no output schema, the description leaves the return shape entirely unexplained — an agent cannot tell whether it receives coupled paths, scores, or rationale. It also doesn't clarify which of change_sets/module_edges is optional given only two required params.

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 0%, so the description must compensate. It loosely maps to three inputs — 'proposed change set' (proposed_paths), 'module edges' (module_edges), and 'historical co-change sets' (change_sets) — but says nothing about the required `files`/`source` corpus, the 200/500/5000 item limits, or which inputs are optional.

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 specific verb and resource: 'Identify files outside a proposed change set that are coupled through supplied module edges, import paths, or historical co-change sets.' The concept is distinct from the sibling tools (hazard detection, error propagation, maintainability), though it does not explicitly name or contrast 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?

Usage is implied rather than stated: knowing which files are coupled to a proposed change set suggests pre-commit impact analysis, but the description never says when to call this versus the sibling audit tools, nor any preconditions. No exclusions or alternatives are given.

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