Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Hash generator, hash toolbox: MD5, SHA-256, SHA-512, Keccak, CRC32 and SRI

pack_hash_toolbox
Read-only

Every common hash of one input in a single call: MD5, SHA-1, SHA-256, SHA-384, SHA-512, Keccak-256 (Ethereum), CRC-32, base64 SHA-256, and Subresource Integrity strings (sha256-, sha384-, sha512-) for . Hashes UTF-8 text, or 0x/hex bytes with hex=true. Cheaper than hashing one algorithm at a time. Use for checksums, cache keys, file integrity and comparing digests across systems. Example: text=hello world. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "text": "<text>"
    },
    "name": "pack_hash_toolbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexNotrue to treat text as hex bytes (0x prefix optional)
textYesText to hash (up to 100,000 characters), or hex bytes with hex=true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses cost and payment mechanics ($0.002/call via x402 USDC or card key, first 25 free, failed calls free) and explicitly explains the non-idempotent billing model ('each call is charged, so repeats are not free'), which resolves an otherwise confusing idempotentHint=false. It also states input limits and encoding behavior, adding real context the annotations cannot carry.

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?

Outputs and algorithm coverage are front-loaded, followed by input mode, use cases, and pricing. Every sentence carries information, though the closing pricing/payment sentence is dense and slightly promotional for a tool description.

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?

With no output schema, the description usefully enumerates the returned digest formats and SRI string prefixes so the agent knows what to expect. Input modes, size limits, and billing are covered; only output ordering/shape (e.g., a map keyed by algorithm name) is left unstated.

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 both parameters are already documented in the schema. The description restates the UTF-8 versus 0x/hex byte mode and the 100,000-character cap but adds no new syntax or edge-case detail beyond what the schema provides, so the baseline 3 applies.

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?

The description names a specific operation (compute every common hash of a single input) and enumerates the exact algorithms and output encodings produced: MD5, SHA-1/256/384/512, Keccak-256, CRC-32, base64 SHA-256, and SRI strings. The line 'Cheaper than hashing one algorithm at a time' implicitly distinguishes it from a single-algorithm sibling, so an agent can route without inspecting schemas.

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?

It gives concrete use cases (checksums, cache keys, file integrity, comparing digests across systems) and an example invocation, plus an implicit routing rule for multi-algorithm needs versus single-algorithm calls. It stops short of explicitly naming the sibling tool or stating when NOT to use this one (e.g., for HMAC or password hashing).

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.