Skip to main content
Glama

list_findings

Retrieve project findings recorded by Tares and external agents, newest first, filtered by entity or agent. Read them before concluding to build on what is known.

Instructions

The findings recorded in the project, newest first: its Tares agents' and the ones external agents recorded. entity and agent narrow them. Read them before concluding, so you build on what is known instead of repeating it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
limitNo
entityNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does disclose that results are ordered newest-first and that both internal and external agent findings are included, which the schema does not say. It is silent on result-set truncation, the default of 20 items, and behavior when `project` is empty or unknown — material details for an unrestricted read.

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?

Three short sentences with the scope and ordering front-loaded and no filler. The backticked parameter names make the filtering clause scannable, though the sentence flow across the line break is slightly awkward.

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?

Output schema exists, so return values need no prose, but the description omits that only a limited page (default 20) is returned while simultaneously urging the agent to read before concluding — an agent could treat a truncated page as the complete record. The unexplained `project` parameter compounds the gap for a four-parameter listing tool with zero schema coverage.

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%, and the description only explains two of the four parameters ("`entity` and `agent` narrow them"). `limit` and `project` receive no explanation beyond the phrase "in the project", leaving the agent to guess at default page size and empty-project behavior.

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?

The description names the resource (findings recorded in the project), the ordering (newest first), and the contributing sources (its own agents plus external agents), which is more than a restatement of the name. It does not distinguish itself from the sibling `recurring_findings`, so an agent must infer the boundary between the two.

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?

"Read them before concluding, so you build on what is known instead of repeating it" gives a genuine when-to-use directive with a rationale, and it hints that `entity`/`agent` narrow the result set. It offers no when-not guidance and names no alternative tool for the filtered or recurring cases.

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