Skip to main content
Glama

Compute HMAC

bursia_hmac
Read-onlyIdempotent

Compute an HMAC (sha256 or sha512, hex) of a message with a key. Use test keys only; nothing is stored or logged. Pure computation, 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": "bursia_hmac"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe secret key. Use test keys only.
messageYesThe message to sign.
algorithmNosha256 (default) or sha512.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / algorithm / description
      Added value: +"sha256 (default) or sha512."
    • addedInput schema / properties / algorithm / enum
      Added value: +[
      +  "sha256",
      +  "sha512"
      +]
    • addedInput schema / properties / key / description
      Added value: +"The secret key. Use test keys only."
    • addedInput schema / properties / message / description
      Added value: +"The message to sign."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new facts: nothing is stored or logged, it is free, and the output is a hex digest. That no-logging and cost disclosure is exactly the kind of context annotations cannot carry.

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 tight sentences, front-loaded with the operation and output format, then the safety/cost caveat. No filler and nothing buried.

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?

With no output schema, the description usefully states the return is a hex digest, and it discloses cost and logging behavior. Only minor gaps remain, such as whether message/key accept arbitrary UTF-8 or require specific encodings.

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 per-parameter descriptions and an enum for algorithm, so the schema does the heavy lifting. The description only echoes the algorithm list and 'test keys only' constraint, adding no new semantics such as encoding expectations for message or key.

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 (Compute) and resource (HMAC of a message with a key), plus algorithm options and output encoding (hex). It does not distinguish itself from the sibling bursia_hash, which an agent would plausibly confuse it with.

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 purpose makes the use case largely self-evident for a pure crypto helper, and 'Use test keys only' sets a constraint. However, it never says when to pick this over bursia_hash, nor does it state any exclusions or prerequisites beyond the key warning.

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