Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

HMAC signature: sign a message with an HMAC (SHA-256 and others) and a key, or check a webhook signature

hmac
Read-only

Compute an HMAC of a message with a key using SHA-256 (default), SHA-1, SHA-384 or SHA-512, in hex and base64. Use to check webhook signatures. The key is used only for this call and is not stored. Example: message=hello, key=secret. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
keyYesThe key
messageYesThe message
algorithmNosha256 (default), sha1, sha384 or sha512

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds genuinely new context beyond the annotations: the key is not persisted after the call, calls are billed at $0.002 (first 25 free), and failed calls are not charged. The 'repeats are not free' note usefully reinforces the idempotentHint=false annotation. 'Reads or computes only and changes nothing' merely restates readOnlyHint/destructiveHint, which is the only wasted motion.

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?

Dense but front-loaded: purpose and algorithms first, then the use case, then the security and billing constraints. Nearly every clause carries distinct information; only the 'changes nothing' clause duplicates annotation content.

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?

Covers cost, key handling, and algorithm choice well, but leaves the response shape ambiguous — 'in hex and base64' could mean both are returned or one is selectable, and with no output schema the agent cannot resolve this. The title's 'check a webhook signature' also implies a comparison capability the three parameters do not support, so the agent may expect verification rather than computation.

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?

Schema coverage is 100%, with all three parameters documented including the algorithm default. The description's example (message=hello, key=secret) illustrates usage but adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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?

Names a specific operation (compute HMAC of a message with a key), enumerates the supported algorithms with SHA-256 as default, and states the output encodings (hex and base64). It is clearly distinct from the sibling `hash` tool by virtue of the key requirement, though it never says so explicitly.

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?

Gives a concrete use case — 'Use to check webhook signatures' — which tells the agent when this tool is relevant. It offers no exclusions or explicit alternative-routing (e.g., when to use the unkeyed `hash` sibling instead), so it stops short of full when/when-not 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.