QuickBuild token-saver tools + x402

util_hash

Read-onlyIdempotent

[PAID $0.005 USDC per call via x402 on Base; errors are free] UTF-8 text (GET ?text= or POST JSON {"text": "..."}, max 100000 chars) hashed with SHA-256, SHA-512, SHA3-256 and keccak256 (0x-prefixed, as used by Ethereum). Missing/oversized text = 400, never charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`text`	No	UTF-8 text to hash (max 100000 chars)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses critical behavior: paid calls at $0.005 USDC via x402 on Base, errors are free, max 100000 chars, and 400 responses are never charged. It also clarifies output formatting for keccak256 as 0x-prefixed Ethereum style.

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 compact and front-loads the payment model, then packs input methods, algorithms, output format, and error behavior into minimal space. It is dense but every clause carries actionable information, with only slight density cost.

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?

For a one-parameter, read-only, idempotent tool with no output schema, the description covers pricing, input formats, limits, error handling, and algorithm outputs well. It does not detail the exact response object keys, but the essential return-value semantics are conveyed.

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?

The schema already covers the single optional parameter at 100% description coverage, including its max length. The description reinforces max length and input transport but does not add new semantic meaning about the parameter beyond what the schema provides, so baseline 3 applies.

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 states a precise verb (hashed) and resource (UTF-8 text), and enumerates the exact hash algorithms returned, including Ethereum-style 0x-prefixed output. An agent can immediately identify this as a multi-algorithm hashing utility with no ambiguity among sibling tools.

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?

It clearly explains input modes (GET ?text= or POST JSON body), the maximum length, and error behavior for missing or oversized input. It does not explicitly name alternatives or when-not-to-use, but no sibling tool overlaps with hashing, so the context is sufficiently clear.

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

All QuickBuild token-saver tools + x402 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?