Skip to main content
Glama

Get review findings in detail

get_findings
Read-onlyIdempotent

Read stored detector findings for a board the signed-in user can review. Pass up to ten exact finding_ids from review_board. Returns original observations, detector priority, assumptions and limitations. verifyWith calls inspect schematic or PCB anchors only, not the engineering conclusion. anchorsAvailable (legacy alias verifiable) says whether those anchor calls exist; a board-wide observation can still be checked against source geometry or requirements. Deterministic means repeatable extraction, not a confirmed defect. Requires board review permission; unrelated public boards are excluded.

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": {
      "board": "<board>",
      "finding_ids": "<finding_ids>"
    },
    "name": "get_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesA personal board, or an organisation board with read:org consent and check permission: handle/slug or a boardrepo.com URL. Discover it with list_my_boards; do not guess one.
versionNoWhich saved version to read: a version number (3 or "v3"), a versionId from list_board_versions, "latest", or a release tag such as "rev-A". Omit for the latest version. Results echo the version they read; pass its id back to stay on it.
finding_idsYesfinding_id values exactly as returned by review_board. Do not guess one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses permission requirements, the exclusion of unrelated public boards, the legacy alias 'verifiable' for anchorsAvailable, and the crucial caveat that 'deterministic' means repeatable extraction rather than a confirmed defect. Those clarifications directly prevent an agent from over-claiming that a finding is a verified bug.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and parameter guidance are front-loaded, but the middle of the description is dense and mixes return-value enumeration ('original observations, detector priority, assumptions and limitations') with caveats, and that return detail duplicates the output schema. The anchor/alias sentence is jargon-heavy and would read better as a short separate clause.

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?

For a read-only, three-parameter tool with an output schema and full annotation coverage, the description supplies everything an agent needs: permissions, id provenance, version echo behavior (in schema), and the interpretive limits of the returned verification flags. Nothing material is left to inference.

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 description coverage is 100%, so board, version and finding_ids are already fully documented in the schema. The description mostly restates the ten-item cap and adds only provenance (

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?

Opens with a specific verb+resource+scope: 'Read stored detector findings for a board the signed-in user can review.' It ties itself to review_board as the source of finding_ids, which lets an agent distinguish this detail-fetch from the listing/summary siblings. It never explicitly contrasts with get_checks or query_design, so differentiation is implied rather than stated.

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 a clear workflow: get finding_ids from review_board, pass up to ten exact ids, do not guess. It also sets preconditions (board review permission, public boards excluded) and warns that verifyWith covers anchors only, not the engineering conclusion. It stops short of naming an explicit when-not-to-use case beyond the permission exclusion.

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