Skip to main content
Glama

read_compile_log

Parse raw Source compiler output into structured findings that explain each message and correct misleading errors, such as leaks without locations and displacement errors showing brush id 0.

Instructions

Turns compiler output into structured findings, each with what the message actually means. Use it on a log someone else produced, or on one from an editor. Several Source messages name the wrong thing -- a leak gives no location, a displacement error always prints brush id 0 -- so each finding carries the correction.

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": {
      "text": "<text>"
    },
    "name": "read_compile_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesRaw compiler output.

Output Schema

NameRequiredDescriptionDefault
cleanYes
byRuleYes
leakedYes
findingsYes
bySeverityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.24-alpha

TDQS

A3.5/5.0
Behavior3/5

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

No annotations beyond a title, so the description carries the full disclosure burden. It does valuable work disclosing that Source messages are misleading (leaks without locations, displacement errors printing brush id 0) and that findings carry the correction, but it says nothing about purity, side effects, size limits, or truncation behavior.

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 tight sentences: purpose first, then usage context, then the correctness caveat. Minor redundancy between 'what the message actually means' and 'each finding carries the correction', but nothing wasted.

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 an output schema present the description needn't explain return values, and a single well-documented parameter keeps the surface small. It covers purpose, when to use, and the non-obvious correction behavior; only input-size/format expectations are unaddressed, which is a minor gap.

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?

One parameter at 100% schema coverage means the schema already documents 'text' as raw compiler output. The description adds no format detail such as whether it takes a whole log, a fragment, or how multiple messages are delimited, so it meets only the baseline.

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 definition states a specific transformation: compiler output in, structured findings out, with each finding carrying an interpretation of the message. It clearly implies this is a parser rather than a compiler runner, though it never names run_compile or read_vmf_lint to sharpen the distinction.

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?

It gives usage context ('on a log someone else produced, or on one from an editor'), which tells the agent it consumes existing raw text. It stops short of explicit exclusions or naming a sibling as the alternative, leaving the boundary with run_compile and read_leak implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.