Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

hash

[x402 paid: $0.003 USDC on Base] SHA digest of any text: sha1/sha256/sha384/sha512, hex or base64 output. tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault
encNoexample: hex
algoNoexample: sha256
textNoexample: hello

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 the full burden and does add real value by disclosing the x402 price ($0.003 USDC on Base) and that tools/call surfaces a live payment challenge. However, it leaves important behavior unexplained: whether a normal call returns a challenge instead of a digest, how payment is completed, and what defaults apply for the optional algo/enc parameters. Useful but incomplete for a zero-annotation tool.

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 sentences plus a bracketed pricing tag; the capability and the algorithm/encoding ranges are front-loaded. The payment-challenge clause is slightly cryptic and could be phrased more precisely, but nothing is wasteful.

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 three-optional-parameter, no-output-schema tool, the description covers the algorithm space, output encoding, and the payment model, which are the main unknowns. The remaining gap is default behavior when algo/enc are omitted and the exact relationship between the payment challenge and the returned digest.

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%, so baseline is 3, but the description adds meaning the schema does not: it enumerates the valid algorithms whereas the schema only says 'example: sha256', and it clarifies that enc selects hex or base64 output versus 'example: hex'. It still does not state defaults for these optional parameters.

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 operation and resource: 'SHA digest of any text', and enumerates the supported algorithms (sha1/sha256/sha384/sha512) plus output encodings. It is immediately distinguishable from all listed siblings, which are price/gas/news/chat utilities with no hashing counterpart. No explicit sibling contrast, which keeps it off a 5.

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?

The phrase 'SHA digest of any text' implies the use case, but there is no statement of when to choose this over anything else, no prerequisites beyond the payment note, and no exclusions. The payment mechanics ('tools/call returns the live payment challenge') give operational context but not selection guidance.

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