Skip to main content
Glama

Attify

List findings

list_findings
Read-onlyIdempotent

The public sample audit's findings: each a template sentence over its numbers, with the evidence tier, sample size and the evidence ids it rests on. Filter by kind: gap_driver, contact_reason, evidence_tier, judge_validation, provenance, window_sensitivity, no_request, handoff_outcome, claim_rule, rule_choice. A vendor's published score lists its drivers only (it quotes no conversation).

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
kindNoe.g. "gap_driver" or "contact_reason".
vendorNoA published vendor's profile slug, e.g. "acme-ai-resolve-bot". Omit for the public sample audit (synthetic demo data, labelled as such).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context beyond that: findings include evidence ids and sample sizes, public sample data is synthetic, and vendor-published scores quote no conversation.

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 description is dense but mostly front-loaded: it defines the resource, lists filter values, then adds the vendor caveat. The long inline list of kind values is useful but would be clearer as structured text; otherwise there is little wasted wording.

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?

For a two-parameter read-only list tool with no output schema, the description covers the return content well: sentences, evidence tier, sample size, evidence ids, and filter kinds. It does not mention ordering, pagination, or default limits, but those are minor for this tool's apparent scope.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds meaningful parameter detail by enumerating the full set of kind values rather than only giving e.g. examples. It also explains that vendor results are limited to published drivers and do not quote conversation, which clarifies the vendor filter.

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 that the tool returns the public sample audit's findings and describes what each finding contains, including template sentence, evidence tier, sample size, and evidence ids. It also distinguishes the vendor case from the public sample case, although the verb 'list' is only implied through the name and title.

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?

The description explains filtering by kind and notes that vendor scores only list drivers, but it does not explicitly say when to use this tool versus sibling tools such as get_evidence or explain_provenance. Usage is implied rather than instructed.

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