Skip to main content
Glama

hash_text

Hashes text with one or more algorithms (MD5, SHA-1, SHA-256, SHA-512, SHA3-256) to create checksums for verification, comparison, or OSINT analysis.

Instructions

Hash a string with one or more algorithms (md5, sha1, sha256, sha512, sha3_256...).

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_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
algorithmsNomd5,sha1,sha256,sha512

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing beyond the operation itself. It does not say whether the result is returned as hex or base64, how multiple algorithm results are keyed or ordered, whether hashing is case/encoding sensitive, or whether the call is pure and side-effect free.

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?

A single compact sentence with the verb and resource front-loaded and the algorithm list parenthetically scoped. Nothing is wasted, though there is also very little present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the definition should at minimum describe the return shape (one digest per requested algorithm, and in what format). For a two-parameter tool where the schema documents nothing, the description leaves the agent guessing on both input formatting and output interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain both parameters. It only loosely covers 'algorithms' by listing example names, and never states that the value is a comma-separated string (the schema's default 'md5,sha1,sha256,sha512' is the only hint), nor what happens when it is omitted. The 'text' parameter gets no clarification at all.

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 gives a specific verb ('Hash') and resource ('a string') and enumerates the supported algorithms, so an agent immediately knows what it does. It stops short of differentiating itself from a sibling like favicon_hash, which hashes a different resource, but the operation itself is unambiguous.

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 only implied: the tool hashes arbitrary text, and the agent must infer that this is the right choice when it needs a digest of a value rather than of a URL or favicon. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative.

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