Skip to main content
Glama

Developer Utilities & Validators (Tanod)

hmac_sign_verify

Read-onlyIdempotent

utilpeek: Returns the HMAC of a message under a shared key (sign), or whether a signature matches it in constant time (verify); handles GitHub (sha256= prefix accepted), Stripe v1 (of {t}.{raw body}) and Slack v0 (of v0:{timestamp}:{raw body}) webhook signatures. For plain digests use hash_text; for JWTs use verify_jwt. Input: mode, message, key, optional key_encoding, algorithm, output and, for verify, signature. Malformed hex or base64, a sha*= prefix naming another algorithm, or verify without a signature is a 422 (not charged). Other prefixes (v0=, v1=) are not stripped. sha1 is for legacy webhooks only. The key and message are never echoed. Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/verify-webhook-signature-hmac-api.html

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

Input Schema

NameRequiredDescriptionDefault
keyYesThe shared secret (at most 1 KiB), read as `key_encoding`. Never echoed or logged.
modeYessign (compute the HMAC) or verify (check `signature`).
outputNoSignature encoding: hex (default) or base64.hex
messageYesThe signed payload exactly as received (e.g. the raw webhook body), as text; at most 64 KiB as UTF-8.
algorithmNosha256 (default), sha512, or sha1 (legacy webhooks only).sha256
signatureNoverify only: the signature to check, in `output` encoding. A `sha256=` style prefix (GitHub's X-Hub-Signature-256) is stripped when it names `algorithm`.
key_encodingNoutf8 (default), hex or base64 (standard alphabet).utf8

Output Schema

NameRequiredDescriptionDefault
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
validNo
outputNo
algorithmNo
signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / algorithm / title
      Removed value: -"Algorithm"
    • removedInput schema / properties / key / title
      Removed value: -"Key"
    • removedInput schema / properties / key_encoding / title
      Removed value: -"Key Encoding"
    • removedInput schema / properties / message / title
      Removed value: -"Message"
    • removedInput schema / properties / mode / title
      Removed value: -"Mode"
    • removedInput schema / properties / output / title
      Removed value: -"Output"
    • removedInput schema / properties / signature / default
      Removed value: -null
    • removedInput schema / properties / signature / title
      Removed value: -"Signature"
    • removedInput schema / title
      Removed value: -"hmac_sign_verifyArguments"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "algorithm": {
      +      "enum": [
      +        "sha256",
      +        "sha512",
      +        "sha1",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "output": {
      +      "enum": [
      +        "hex",
      +        "base64",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "signature": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "valid": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds materially more: malformed hex/base64, a mismatched `sha*=` prefix, or verify without a signature yields a 422 that is not charged; other prefixes (`v0=`, `v1=`) are not stripped; key and message are never echoed or logged; typical latency under 0.1s and the price/free-quota model.

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?

Front-loads the sign/verify purpose and the provider coverage before the operational caveats, and reads as a tight single block. The pricing, latency, and docs-link sentences are useful but slightly dilute an otherwise dense, well-ordered definition.

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

Completeness5/5

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

For a sign/verify tool with an output schema already present, the description covers everything an agent needs: alternatives, error triggers, prefix handling, encoding behavior, and secret-handling guarantees. Nothing material about correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description goes beyond it: it tells the agent how to build the signed payload for Stripe and Slack and that GitHub's `sha256=` prefix is accepted, and warns that `v0=`/`v1=` prefixes are not stripped. That is real semantic guidance an agent cannot get from the schema alone.

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?

States a specific verb pair and resource: returns the HMAC of a message under a shared key (sign), or checks a signature in constant time (verify). It also enumerates the exact webhook dialects handled (GitHub `sha256=`, Stripe `v1` over `{t}.{raw body}`, Slack `v0` over `v0:{timestamp}:{raw body}`), which no sibling does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent away from two named siblings: "For plain digests use hash_text; for JWTs use verify_jwt." Adds a further usage boundary — sha1 is for legacy webhooks only — and names the input conditions that produce a 422 rather than a result.

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.