Skip to main content
Glama

dev_tools_hmac

[$x402 pago por llamada] Calcula un HMAC con SHA-1, SHA-256 o SHA-512.

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": {
      "key": "<key>",
      "message": "<message>"
    },
    "name": "dev_tools_hmac"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesClave secreta.
algoNoAlgoritmo de hash. Por defecto `sha256`.
messageYesMensaje a autenticar.
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?

With no annotations, the description carries the full burden and does disclose the important non-obvious trait: it is a paid, per-call tool ('$x402 pago por llamada'), and the x_payment param confirms a 402 fallback. However it omits the output encoding (hex vs base64) and asserts nothing about being a pure/read-only computation, leaving real behavioral gaps.

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?

A single terse sentence with no filler, and the payment notice is front-loaded. Slightly cryptic bracket notation and a mixed-language description cost a point on clarity, but nothing is wasted.

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?

For a 4-parameter tool with no annotations and no output schema, the definition should clarify the return value (digest encoding) and the full 402 flow. The payment hint is present but the output format and error behavior are not, leaving the agent to infer too much.

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, but the description adds the concrete algorithm values that the schema leaves unspecified ('Algoritmo de hash' has no enum). It also surfaces the payment dimension that the x_payment parameter implements, giving useful extra meaning.

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 ('Calcula un HMAC') and enumerates the supported algorithms (SHA-1, SHA-256, SHA-512), which distinguishes it from the plain-hash sibling dev_tools_hash. It does not explicitly name that sibling, so differentiation is implicit rather than spelled out.

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: an agent can infer 'use this to authenticate a message with a secret key'. There is no explicit guidance on when to prefer this over dev_tools_hash or dev_tools_totp, and no statement of prerequisites beyond the payment tag.

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