Skip to main content
Glama

Hash Generator API - MD5, SHA-1, SHA-256, SHA-512 of text or a file

hash_generator
Read-onlyIdempotent

Hash text or a file with MD5, SHA-1, SHA-256 and SHA-512, and compare against a hash you already have. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/hash-generator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
textNoThe text
filesNoOr several files: [{fileName, fileContent (base64)}]
fileNameNoFile name with extension, e.g. report.pdf
compareWithNoA hash you have, to compare (optional)
fileContentNoOr send a file as base64 (a data: URI is fine) instead of text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

It provides critical operational context beyond the annotations, such as the safety guarantee of server-side deletion of files after the call, and details regarding rate limits and associated costs.

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 description is concise and front-loads the core function before detailing operational constraints. It uses the information efficiently, though the inclusion of pricing information is slightly verbose.

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?

The definition is highly complete for an API hashing tool. It covers the core functionality, operational safety (data deletion), and consumption details (rate limits/pricing), addressing all likely agent concerns.

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?

Given that the schema coverage is 100%, the description primarily restates the functional purpose of the parameters (text, files, comparison). It does not add deep semantic meaning that goes beyond what the structured schema provides.

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 clearly states the purpose as hashing text or files using specific algorithms (MD5, SHA-1, SHA-256, and SHA-512) and includes the capability to compare results against existing hashes.

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?

The description provides clear usage contexts (hashing text, hashing files, and comparison), which assists in determining when to invoke the tool correctly, although it does not explicitly name alternative tools for comparison.

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.

Resources