Skip to main content
Glama

Format SEI CERT findings as a report

format_findings
Read-onlyIdempotent

Formats CERT code review findings as Markdown, GitHub, GitLab, SARIF, or Code Quality payloads without posting, enabling draft review before submission.

Instructions

Render findings as a report or review payload without sending it. style: markdown (string); github (object for POST /repos/{owner}/{repo}/pulls/{n}/reviews, event COMMENT, one comment per finding); gitlab (array of merge-request discussion bodies; position SHAs are placeholders to fill from diff_refs); sarif (SARIF 2.1.0 object); codequality (GitLab Code Quality array); gitlab-sast (GitLab SAST report object). Use as the last step, then show drafted comments to the user before anyone posts them. Pass findings unchanged from check_files/check_diff findings or validate_findings accepted. Pure formatting: no files, network or posting.

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": {
      "findings": "<findings>"
    },
    "name": "format_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute repository root; file paths in the output are made relative to it. Omit and paths become relative to the server's working directory.
styleNoOutput format; see the tool description for each shape.markdown
findingsYesFindings exactly as returned by check_files, check_diff (findings) or validate_findings (accepted).
warningsNo`warnings` from check_files/check_diff; shown as a partial-analysis notice in markdown, github and sarif.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent and closed-world, so the bar is low, yet the description adds real behavioral detail: github style maps to a POST /repos/.../reviews payload with event COMMENT and one comment per finding, gitlab positions are placeholder SHAs to fill from diff_refs, and warnings appear as a partial-analysis notice in markdown/github/sarif. It also states plainly that nothing is written, posted or sent.

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?

Front-loaded with the core action and its non-posting guarantee, then a compact style key, then the workflow rule. The dense semicolon-separated style list is efficient rather than padded; nearly every clause carries decision-relevant information.

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?

Covers what an agent needs to choose a style, source the findings, and handle the drafted output, and the style entries effectively describe the return shapes despite no output schema. Minor gap: no guidance on the `warnings` parameter's expected values or on which style to pick for a given downstream consumer.

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%, so the baseline is 3, but the description adds meaning beyond the enum: it explains each style's concrete output shape and that findings must be passed unchanged from upstream tools. The `root` path-relativization behavior is left to the schema, which covers it well.

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 ("Render findings as a report or review payload") plus a scope limiter ("without sending it", "Pure formatting: no files, network or posting"), which separates it from posting/review-packet siblings. The per-style breakdown makes the output surface concrete.

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?

Gives explicit sequencing ("Use as the last step"), a workflow rule ("show drafted comments to the user before anyone posts them"), and names the exact upstream sources and fields (check_files/check_diff `findings`, validate_findings `accepted`). It does not explicitly name what to use instead when the agent does want to post, so it stops short of full when/when-not/alternative coverage.

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