Skip to main content
Glama

SizeMyFile

Calculate a file checksum

hash
Idempotent

Read any file in chunks and calculate SHA-256. Bounded processing; 32 MiB combined input per operation, at most 50 files. Queues a run and returns its ID for progress and output tracking. Uses cloud allowance.

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": {
      "artifacts": "<artifacts>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
artifactsYes
idempotency_keyYes
allow_server_fallbackNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing bounded processing limits (32 MiB combined input, max 50 files), that the operation queues an async run rather than returning results inline, and that it consumes cloud allowance. These are exactly the operational facts an agent needs before calling. It does not explain what happens on limit violation or failure, which keeps it from 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?

Four short sentences with the core action front-loaded and limits immediately after. No filler. Slightly dense in that constraints, async behavior, and billing are packed into one run of sentences without structural separation.

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?

An output schema exists, so return values need no explanation, and the async run/ID model is covered. However, for a tool with a required idempotency_key, a defaulted allow_server_fallback flag, and nested options, the description leaves key invocation semantics and error behavior unaddressed.

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?

With 0% schema description coverage and 4 parameters, the description must carry the load, and it only partially does. The '32 MiB combined input / at most 50 files' constraint adds real meaning beyond the schema, but the required idempotency_key and the allow_server_fallback flag (what 'fallback' means here) are never explained, nor is the empty options object.

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?

Names a specific verb and result: read files in chunks and calculate SHA-256 checksums. That is unambiguous and clearly distinct from siblings like hex_view or data_compare. It stops short of explicitly saying how it differs from a hypothetical alternative, but the purpose itself is concrete.

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: 'Queues a run and returns its ID for progress and output tracking' hints at the async workflow (poll with get_run), but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer the context but is not guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.