Skip to main content
Glama

File checksum

nas_file_checksum
Read-only

Compute MD5 or SHA-256 checksums for NAS files to verify transfers and file integrity, with per-file timeouts for large files.

Instructions

Compute the MD5 or SHA-256 checksum of files on the NAS, for example to verify a transfer. The NAS reads each whole file, so large files take a while: timeout_seconds applies to each file, and a file that needs longer fails with "context deadline exceeded". The result has items[], one per path; check each for success.

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": {
      "algorithm": "<algorithm>",
      "paths": "<paths>"
    },
    "name": "nas_file_checksum"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesFiles to hash. Absolute NAS paths (1 to 20).
algorithmYesChecksum algorithm.
timeout_secondsNoTime limit in seconds (default 300, max 1800). Raise it for large folders or files; a result cut off by the limit is incomplete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, the description discloses real behavioral traits: every file is read in full, large files are slow, the timeout is applied per file, and a slow file fails with 'context deadline exceeded'. It also warns that results must be checked item-by-item for success. It does not mention permission or authentication requirements, which keeps it short of a 5.

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?

Purpose is front-loaded in the first clause, then cost, then failure mode, then result shape. Four sentences with little waste, though the 'check each for success' hint could be folded into the result sentence.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so by describing items[] as one entry per input path and flagging that each needs a success check. Combined with the timeout and failure-mode detail, an agent has everything needed to call it correctly.

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 the baseline is 3. The description does add one useful nuance the schema lacks: that timeout_seconds is enforced per file rather than across the whole batch, which changes how an agent should size the value.

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 specific verb+resource: 'Compute the MD5 or SHA-256 checksum of files on the NAS', which clearly separates it from siblings like nas_file_read or nas_file_stat. It adds a motivating use case ('verify a transfer') but does not explicitly name an alternative tool for overlapping needs.

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 phrase 'for example to verify a transfer' implies when the tool is appropriate, and the timeout discussion hints at size constraints, but there is no explicit when-to-use vs when-not guidance or reference to a sibling for related operations.

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