Skip to main content
Glama

dev_tools_hash

[$x402 pago por llamada] Hashea un texto con MD5 o SHA-256.

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

Input Schema

NameRequiredDescriptionDefault
algoNoAlgoritmo a usar. Por defecto `sha256`.
textYesTexto a hashear.
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose the notable commercial behavior: pay-per-call via x402. That is real added context, but it omits anything about output encoding (hex vs base64), determinism, or error behavior on invalid algorithms, which matters for a codelessly documented utility.

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?

Two compact clauses, with the payment-model tag front-loaded before the core purpose. Nothing is wasted and no filler is present.

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-parameter, single-purpose utility with full schema coverage and the x402 payment mechanics documented in the x_payment property, the description is close to sufficient. The only real gap is the shape of the returned digest, which an agent may need to chain into another call.

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 the baseline is 3, and the description earns a bump by enumerating the actual algorithm choices (MD5, SHA-256), which the schema only alludes to via "Por defecto sha256" without listing accepted values. It still doesn't confirm the literal token strings an agent must pass.

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 ("Hashea un texto") and names the supported algorithms (MD5/SHA-256), so an agent knows exactly what the tool does. It does not, however, distinguish itself from near-siblings like dev_tools_hmac or dev_tools_hex, leaving the agent to infer the boundary.

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?

The description gives no indication of when to prefer this over dev_tools_hmac (keyed hashing) or when a hash is the wrong tool. There are no exclusions, prerequisites, or alternative routes named anywhere in the text.

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