Skip to main content
Glama

get_hash

Paid $0.02 (x402, USDC Base): cryptographic hash of any text via WebCrypto. Args: text (string), algo (sha256 default | sha1 | sha384 | sha512).

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": "get_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
algoNo
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries real weight here: it discloses that the call costs $0.02 via x402 (USDC on Base), which is important pre-invocation context an agent would otherwise not know. It does not disclose the output encoding (hex, base64, or byte array) or whether the text is hashed as UTF-8, both of which materially affect how a result is interpreted.

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?

Two compact clauses: cost first, then args. Every phrase carries information and nothing is padding, though leading with pricing rather than the operation slightly delays the core purpose.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only source of behavioral detail, and it omits the critical return format (string encoding of the digest) along with input encoding assumptions. It is otherwise complete for a simple two-parameter utility.

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

Parameters4/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 carry parameter meaning, and it covers both params and supplies the non-obvious default ('sha256 default'). It adds little about 'text' beyond its type and does not address length limits or character encoding.

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?

States a specific verb and resource ('cryptographic hash of any text') plus the mechanism ('via WebCrypto'), which no sibling tool (gen_uuid, encode_base64, gen_password) offers. An agent can identify the function without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance, and no alternatives named for adjacent tasks such as encoding or UUID generation. The only guidance is a default algorithm value, which is parameter detail rather than usage context.

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