Skip to main content
Glama

List findings

vestige_list_findings
Read-only

Lists evidence-linked findings for a software artifact, with optional filters by kind and confidence plus pagination. Use it to review and page through verified technical findings for a target.

Instructions

List evidence-linked findings for a target, optionally filtered by kind or confidence, with pagination.

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": {
      "artifactId": "<artifactId>"
    },
    "name": "vestige_list_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
offsetNo
artifactIdYes
confidenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results are paginated and that filtering is optional, which is real behavioral context beyond the annotations, but it omits default page size, max limit, and ordering of results.

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?

A single front-loaded sentence with no filler; the core action and modifiers come first. It is short enough to be efficient, though the terseness contributes to the parameter ambiguity noted above.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A listing tool with five parameters at 0% schema coverage and no output schema needs more than one sentence: the shape of a returned 'finding', the meaning of evidence-linking, and valid kind/confidence values are all left unexplained. The definition is too thin for the complexity an agent must navigate.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description carries the full burden. It names kind, confidence, and pagination, but gives no allowed values or format for kind and confidence (both free-form strings with no enums), and never explains that artifactId identifies the 'target' or that limit caps at 1000.

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?

States a specific verb and resource: 'list evidence-linked findings for a target', which is clearly a read/list operation on findings. It does not explicitly distinguish itself from siblings like vestige_get_evidence or vestige_list_targets, so an agent must infer the boundary rather than being told.

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?

'optionally filtered by kind or confidence, with pagination' implies how to narrow results, which is mild usage guidance. There is no explicit when-to-use versus siblings (e.g., get_evidence vs list_findings) and no when-not-to-use or prerequisite guidance.

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