Skip to main content
Glama

Hash text

bursia_hash
Read-onlyIdempotent

Hash a text with sha256, sha1, sha512 or md5. Returns the hex digest. Use to fingerprint content or compare files by checksum. Pure computation, 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": "bursia_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to hash (UTF-8).
algorithmNoHash algorithm. Default sha256.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / algorithm / description
      Added value: +"Hash algorithm. Default sha256."
    • addedInput schema / properties / algorithm / enum
      Added value: +[
      +  "sha256",
      +  "sha1",
      +  "sha512",
      +  "md5"
      +]
    • addedInput schema / properties / text / description
      Added value: +"The text to hash (UTF-8)."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: 'Returns the hex digest' (output format, valuable since there is no output schema) and 'Pure computation, free' (no side effects, no cost/rate-limit concern). That is useful added value beyond the annotations, though nothing is said about input size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero waste: what it does, what it returns, and when to use it — all front-loaded. Every sentence earns its place.

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, side-effect-free tool with no output schema, the description covers the operation, the return format (hex digest), and the use case. Nothing an agent needs in order to call it correctly 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% and the schema itself documents the UTF-8 text input, the enum of algorithms, and the sha256 default. The description restates the algorithm list but adds no syntax or format detail beyond what the schema already provides, so the 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?

States a specific verb and resource ('Hash a text') and enumerates the four supported algorithms, so the operation is unambiguous. It does not explicitly distinguish itself from the sibling bursia_hmac, which an agent could reasonably confuse with a plain hash; the differentiation is only implicit in the absence of a key parameter.

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?

'Use to fingerprint content or compare files by checksum' gives a clear, concrete context for when to reach for this tool. There are no exclusions or named alternatives (e.g., bursia_hmac for keyed hashing), which keeps it below 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.

Resources