Skip to main content
Glama

Get evidence record

vestige_get_evidence
Read-only

Retrieve a single evidence record by ID and re-authenticate it against its content digest before use, ensuring reports cite verified artifacts.

Instructions

Fetch one evidence record by id. Records are re-authenticated against their content digest before being served.

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": {
      "evidenceId": "<evidenceId>"
    },
    "name": "vestige_get_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidenceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior beyond them: records are re-authenticated against their content digest before being served, warning the agent that a fetch can fail on integrity mismatch rather than simply returning data.

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, front-loaded with the operation and followed by the one non-obvious behavioral fact. Nothing is padded or repeated from the schema.

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

Completeness3/5

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

For a simple read-only fetch the description is close to sufficient, and annotations carry the safety profile. However, there is no output schema, so the agent gets no picture of what an evidence record contains or how errors (digest mismatch, not-found) surface — a gap the description could have closed in a sentence.

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?

Schema coverage is 0% for the single parameter, so the description is the only source of meaning and it says little more than "by id", which largely restates the parameter name evidenceId. It does not describe the id format or origin (e.g., obtained from a prior analyze or list call) that would compensate for the coverage gap.

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?

"Fetch one evidence record by id" gives a specific verb (fetch), a specific resource (evidence record), and a scope (single, by id), which distinguishes it from the list-style siblings such as vestige_list_findings. It never names a sibling explicitly, so it stops short of full differentiation.

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?

Usage is only implied: the agent must already hold an evidenceId to call this, but the description never says so, nor does it route the agent to vestige_list_findings when an id is unknown or to vestige_export_report for bulk retrieval. No exclusions or prerequisites are stated.

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