Skip to main content
Glama

Agent Exchange store

util_hash

$0.001 via x402: sha-256 (default), sha-1, sha-384, sha-512 or md5 of a text as hex and base64, with its byte length. Pay 0.001 USDC through https://store.agentexchange.work/gw/util/hash?text=hello&algo=sha-256 Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
algoNoalgo
textYestext
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

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?

No annotations are provided, so the description carries the full burden, and it does disclose the key behavior: cost ($0.001), the x402/USDC payment flow settled by Coinbase, the gateway endpoint, the default algorithm, and the returned representations. It omits rate limits and failure behavior, but for a stateless hash utility the payment semantics are the load-bearing detail and they are covered.

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

Conciseness3/5

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

The core purpose is front-loaded, but the entry is padded: the price is stated twice ('$0.001 via x402' and 'Pay 0.001 USDC'), and a full example URL is embedded mid-sentence, making it read as a run-on. It is informative but not tight.

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

Completeness4/5

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

With no output schema, the description compensates by stating what is returned (hex and base64 digest plus byte length) and how payment/settlement works. For a three-parameter utility this is close to complete; only error and rate-limit behavior are unaddressed.

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 coverage is 100% but the schema descriptions are bare tokens ('algo', 'text'), so the description adds genuine meaning: the accepted algorithm values and the default. The optional x_payment parameter's purpose is also clarified via the quote-versus-pay flow description, going beyond the schema's terse note.

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 names a specific operation (hashing a text) and enumerates the exact algorithms supported (sha-256 default, sha-1, sha-384, sha-512, md5), plus the output forms (hex, base64, byte length). No sibling tool in the list offers hashing, so an agent can immediately place it without ambiguity.

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 text, and the description surfaces the operational precondition (must pay 0.001 USDC via x402). There is no explicit when-to-use/when-not-to-use statement and no named alternative, but the payment gate is the one condition an agent actually needs to invoke it.

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