Skip to main content
Glama

hash

Read-only

Generate checksums for text or files using MD5, SHA, SHA3, Blake2, or CRC algorithms, optionally with HMAC keys, and verify results against an expected value.

Instructions

Hash text or any-size file: md5 sha1 sha256 sha512 sha3-256 blake2b512 crc32; HMAC via key; expected verifies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
pathNoor a file
textNo
base64No
expectedNo
algorithmsNodefault sha256

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a digest operation, and the description adds real behavior beyond annotations: it accepts arbitrarily large files, switches to HMAC when a key is supplied, and verifies against an expected digest. It stops short of describing the return shape (digest format, verification result), which matters since no output schema exists.

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?

Dense and front-loaded with zero filler, but the telegraphic semicolon fragments push compression too far — 'expected verifies' is cryptic on first read and the file-vs-text relationship is only implied by 'or a file' in 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 six-parameter tool with no output schema and thin schema descriptions, the definition leaves gaps: the return value (raw digest vs verification boolean), the purpose of base64, and how text/path interact are all unstated. It covers the core hashing story well but not enough for an agent to call every parameter confidently.

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 only 33%, and the description compensates for most of it by mapping key→HMAC, path→file, text→input, expected→verification, and algorithms via the algorithm list. But it never mentions the base64 parameter at all, nor clarifies the mutual exclusivity or precedence of text versus path.

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?

States a specific verb (hash) with both accepted resources (text, any-size file) and enumerates the exact algorithm set, which unambiguously separates it from siblings like encode or json. An agent can tell this is a digest/HMAC utility without opening the schema.

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 implied by the fragments: 'HMAC via key' signals keyed hashing and 'expected verifies' signals a compare mode. However, no explicit when-to-use or when-not-to-use guidance is given, and no alternative tool (e.g. encode) is named as a fallback for non-hashing needs.

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