Skip to main content
Glama
cbyrohl

cdash-mcp

by cbyrohl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_build_errors

Fetch compiler errors or warnings for a CDash build, showing source file and line info. Supports filtering by build ID, optional warnings, and pagination with limit and offset.

Instructions

View compiler errors or warnings for a build, with source file and line info.

Args:
    build_id: The CDash build ID.
    warnings: If True, show warnings instead of errors.
    limit: Maximum number of errors to return (default 30, max 200).
    offset: Number of errors to skip (default 0). Use for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
build_idYes
warningsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It correctly signals a read-only operation ('View'), describes the output contents, and documents pagination behavior via limit and offset. It does not mention auth requirements or rate limits, but those are less critical for this simple read operation.

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?

The description is compact, front-loaded with a clear one-sentence purpose, and followed by a clean parameter list. Every line earns its place with no redundant filler.

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?

Given the tool's simple query nature and the presence of an output schema, the description covers all necessary caller-facing behavior: what it returns, how to switch modes, and how to paginate. It could have strengthened cross-tool orientation, but that is not essential for invoking this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully document parameter meaning. It does: build_id is identified as the CDash build ID, warnings toggles errors vs warnings, limit caps the result count, and offset is explicitly tied to pagination. This adds significant value beyond the raw schema.

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?

The description uses a specific verb ('View') and resource ('compiler errors or warnings for a build') and includes what information is returned (source file and line info). This clearly differentiates it from sibling tools focused on tests, coverage, or configuration output.

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 description makes it clear this tool is intended for retrieving compiler errors or warnings, but it does not explicitly state when to prefer it over alternatives or mention any sibling tools. Usage context is implied rather than formally contrasted.

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

Deploy Server

Other Tools