Skip to main content
Glama

snapshot_files

Computes SHA-256 hashes and file sizes for regular workspace files, adding tamper-evident records to evidence bundles while rejecting sensitive files and symlinks.

Instructions

Computes SHA-256 hashes and file sizes for regular files strictly inside the workspace. Rejects sensitive files and symbolic links.

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": {
      "bundleId": "<bundleId>",
      "paths": "<paths>"
    },
    "name": "snapshot_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesList of file paths relative to workspace root.
bundleIdYesThe unique identifier of the evidence bundle.
workspaceNameNoOptional registered workspace/package name (defaults to primary root).
workspacePathNoOptional workspace path hint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / workspaceName
      Added value: +{
      +  "description": "Optional registered workspace/package name (defaults to primary root).",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

B3.4/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, and it does add real value: it states that only regular files strictly inside the workspace are accepted and that sensitive files and symlinks are rejected. What it omits is the consequence of rejection (hard error versus skip-and-continue), whether the computed hashes are persisted into the named bundle or merely returned, and any size or count limits. These are meaningful gaps for a tool that takes a bundleId.

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 with no filler, and the scope/security constraint is stated up front where the agent will read it. Nothing here is redundant with the title or wasteful.

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 four-parameter capture tool with a fully documented schema and no output schema, the description covers the essentials: what is computed, what is accepted, and what is refused. The main residual gap is that 'snapshot' plus a required bundleId implies persistence, yet the description never says whether results are written into the evidence bundle or just returned, which matters for downstream verification steps.

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 description coverage is 100%, so bundleId, paths, workspaceName, and workspacePath are already documented in the schema. The description restates the path constraint ('strictly inside the workspace') but adds no syntax, format, or interaction detail for the workspace resolution parameters. Baseline 3 applies when the schema does the heavy lifting.

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 and resource: computing SHA-256 hashes and file sizes for regular files inside the workspace. That is far more informative than the bare tool name 'snapshot_files'. It stops short of distinguishing this from neighboring evidence-capture tools such as capture_ast_evidence or capture_sbom_evidence, so an agent must infer which capture path fits.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling to prefer for other evidence types. The only implicit guidance is the scope restriction to regular files inside the workspace. An agent has to guess whether this is the right call before recording other evidence.

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