Skip to main content
Glama
Sign In
ellmos-clatcher-mcp

ellmos-clatcher-mcp

Official
by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

checksum

Calculate file hashes (SHA256, MD5, SHA1, SHA512) and optionally verify against an expected hash to ensure file integrity.

Instructions

Calculate file hash (SHA256, MD5, SHA1, SHA512). Optionally verify against expected hash.

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": {
      "path": "<path>"
    },
    "name": "checksum"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the file
expectedNoExpected hash to verify against
algorithmNosha256

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A4.1/5.0
Behavior3/5

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

Description discloses read-only behavior (calculate hash) and optional verification, but lacks details on side effects, permissions, or output format. No annotations exist to supplement.

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?

Single sentence front-loads 'Calculate file hash' and efficiently covers all aspects without waste.

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?

Covers core functionality and algorithms, but lacks output format, error conditions, or behavior when verification fails. No output schema provided.

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?

Adds meaning beyond schema by mentioning optional verification against expected hash. Schema already covers path and algorithm enum, but description ties expected to verify action.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action (calculate file hash) and resource (file hash), with explicit algorithm options. It distinguishes from sibling tools like archive and batch_rename, which are unrelated.

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

Usage Guidelines4/5

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

Description implies usage for hashing files and optional verification. While no explicit when-not or alternatives are provided, sibling tools are distinct, making context clear.

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

Deploy Server

Other Tools