Skip to main content
Glama

evidence_scan

Re-reads evidence folders from verify skills and .projtruth, indexing collected sources by acceptance criterion ID for requirement verification.

Instructions

Re-read the evidence folders and index them by criterion id. Sources: .claude/skills/verify-*/evidence/** and .projtruth/evidence/**.

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": "evidence_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/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 disclosure burden. It usefully names the exact glob sources (.claude/skills/verify-*/evidence/** and .projtruth/evidence/**), but never states that indexing writes or overwrites a persisted index, whether existing entries are dropped, or what the call returns — significant gaps for a state-mutating tool.

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?

Two short sentences, action front-loaded, followed by the source scope. Nothing is redundant and no filler appears.

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?

Given zero parameters, no annotations, and no output schema, the description covers what the tool scans and how it keys the results, which is most of what an agent needs. It falls short only on the persistence/return behavior, which matters because no output schema exists to fill that gap.

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?

The tool takes zero parameters, so the baseline is 4. The description still adds value by defining the implicit input domain (the two evidence path globs) that would otherwise be invisible in an empty schema.

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 a specific action pair (re-read and index) on a specific resource (evidence folders), and states the indexing key (criterion id). It does not explicitly contrast itself with siblings such as status_report or req_list, but the verb+resource is concrete enough that an agent knows this tool rebuilds an evidence index.

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 word 'Re-read' implies refresh semantics — invoke this when the evidence folders may have changed and the criterion-id index is stale. No explicit when/when-not guidance or named alternatives are given, so usage is only implied rather than stated.

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