Skip to main content
Glama

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

SHA256 hash, SHA-256: hash text with SHA-256, SHA-1, SHA-384 or SHA-512

hash
Read-only

SHA256 hash of UTF-8 text (SHA-256 by default; SHA-1, SHA-384 or SHA-512 on request), returned as a digest in hex and base64. Use for checksums, cache keys and deduplication. Example: text=hello. 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": "hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to hash
algorithmNosha256 (default), sha1, sha384 or sha512

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false. The description adds value beyond that by disclosing the return encoding (hex and base64), the billing model ($0.002/call via x402 USDC or card key, first 25 free, failed calls free) and the non-free repeat caveat, which explains why idempotentHint is false. It adds nothing about failure modes or rate limits, so not 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?

The core capability and output format are front-loaded in one sentence, followed by use cases and pricing. The final clause ('each call is charged, so repeats are not free') partially repeats the pricing sentence, a small redundancy, but overall it is tight and well-ordered.

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?

For a two-parameter, non-destructive compute tool with no output schema, the description covers input, algorithm options, return encodings, and cost. Nothing an agent needs in order to call it correctly or decide whether to call it is missing.

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 'text' and 'algorithm' are already documented, including the allowed algorithm values. The description only restates the default and the value list plus a trivial example, adding little meaning beyond the schema; baseline 3 applies.

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?

The description leads with a specific verb+resource ('SHA256 hash of UTF-8 text') and adds scope detail: default algorithm, supported alternatives, and output encoding. It is fully clear on what the tool produces, but it never distinguishes itself from the sibling 'pack_hash_toolbox', so it stops short of a 5.

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 states concrete use cases ('checksums, cache keys and deduplication') and an example invocation ('text=hello'), which gives an agent a clear context for reaching for this tool. There are no exclusions or explicit when-not guidance, so it is a 4 rather than a 5.

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.