Skip to main content
Glama

Inspect Evidence

inspect_evidence
Read-onlyIdempotent

Extract precise technical evidence with SHA-256 hashes and working tree status by reading code lines, symbols, or Git diffs for verification.

Instructions

Trích xuất bằng chứng kỹ thuật chính xác (Tier 3) kèm mã băm SHA-256 và trạng thái Working Tree: đọc dòng code ('file_lines'), đọc symbol ('symbol'), hoặc lấy git diff ('git_diff').

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": {
      "project_id": "<project_id>",
      "targets": "<targets>"
    },
    "name": "inspect_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetsYes
project_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description still adds real information: output carries a SHA-256 hash and Working Tree status, so an agent knows the result is verifiable/anchored evidence rather than a plain file read. Nothing contradicts the read-only annotation; the 'Working Tree' mention implies uncommitted state is included, which is a useful behavioral signal.

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 a precise mode list – no filler and the action verb comes first. The opaque 'Tier 3' label is the one phrase that does not earn its place for an agent without prior context.

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?

An output schema exists, so return values need not be explained, and the three extraction modes are covered. What is missing is handling of multiple targets in one call and any failure/not-found behavior, which keeps it short of fully complete.

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?

The description maps each enum value of 'kind' to an intent, which adds meaning beyond the schema. However, the array-of-objects 'targets' structure and its fields (base_ref, target_ref, start_line, end_line, symbol_name) are not explained at all in the description, and with schema description coverage reported as 0% that gap is not compensated.

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 concrete verb+resource ('Trích xuất bằng chứng kỹ thuật' – extract technical evidence) and enumerates the three modes it supports (file_lines, symbol, git_diff), which lets an agent match it to a task. The only drag is the unexplained qualifier 'Tier 3', which means nothing without external context.

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 colon-list of modes gives implicit guidance on which 'kind' to pick for which intent, but there is no statement of when to choose this tool rather than investigate_codebase or get_project_overview. Prerequisites (e.g., needing an already-scoped project, relative vs absolute paths) are also unstated.

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