Skip to main content
Glama
Kuestenlogik

Bowire MCP

Official
by Kuestenlogik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

bowire.report.rollup

Combine lint, contract, test, benchmark, and scan reports from local files into one row per service for a portfolio-wide view of quality. Reads local report files only; never calls a service.

Instructions

Roll the reports Bowire writes up into one view across services — the portfolio question. Reads lint findings, contract-verification results, benchmark run histories, k6 summaries, scan SARIF and test JUnit from the given paths (directories are walked recursively) and returns one row per service. Purely local: it reads files that already exist and never calls a service. Returns { services: [{ service, worst: high|medium|low|info|null, lint, contracts, tests, benchmark, scanErrors, lastReportAt, sources }], summary: { services, atHigh, clean, skipped } }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoFiles or directories holding Bowire reports. Defaults to the workspace's .bowire folder.
serviceNoAttribute every report to this service instead of inferring it from the report and its path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it declares the tool is 'purely local', reads only files that already exist, never calls a service, and walks directories recursively. It also spells out the return shape since no output schema exists. It stops short of 5 only because it doesn't say what happens when nothing is found beyond the 'skipped' counter.

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?

The purpose and locality constraint are front-loaded, and each sentence carries information (sources, locality, return shape). The trailing return-value sentence is long but earns its place because there is no output schema to carry it.

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?

No annotations and no output schema, so the description must cover both the behavioral profile and the return contract — and it does, listing the sources read, the locality guarantee, and the full response shape with the severity vocabulary. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and both params are documented, so the baseline is 3. The description adds genuine value beyond the schema by stating that directories are walked recursively and that reports are read from the given paths, which clarifies the semantics of the 'from' parameter.

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?

States a specific verb and resource ('Roll the reports ... into one view across services') and frames the scope as 'the portfolio question', which distinguishes it from per-artifact siblings like bowire.lint or bowire.contract.matrix. An agent can identify the aggregate-across-services role without opening the schema.

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?

The description gives clear context for when this tool applies — aggregating existing reports into a portfolio view — and the sources it consumes. It does not name an explicit alternative or a when-not condition (e.g., use bowire.lint for a single fresh lint), so it stops short of full routing guidance.

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