Skip to main content
Glama
Sign In
tool-mcp-server

tool-mcp-server

by maple-awa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

tool_hmac_verify

Verify an HMAC by comparing the computed signature against an expected value using a given key and algorithm. Returns a boolean indicating validity.

Instructions

[crypto] HMAC Verify

Parameters:

  • expectedHmac (string): Expected HMAC

  • data (string): Data

  • key (string): Key

  • algorithm (string): Algorithm

Outputs:

  • valid (boolean): Valid

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tool_hmac_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoKey
dataNoData
validNoValid
algorithmNoAlgorithm
expectedHmacNoExpected HMAC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only lists inputs and the 'valid' output, but does not mention supported algorithms, how HMAC comparison is performed, input encoding expectations, or error behavior. This is minimal and repeats schema content rather than adding meaningful context.

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?

The description is concise and front-loaded with the [crypto] category and purpose. The parameter list duplicates schema information, but the overall length is appropriate for a simple tool and contains no filler.

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

Completeness2/5

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

Given the tool's cryptographic nature, the absence of annotations and output schema makes the description underspecified. It omits crucial details like supported algorithm names, default behavior, required fields, and how the expected HMAC is encoded or compared. The schema's inclusion of 'valid' as an input property adds further ambiguity.

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

Parameters2/5

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

Schema coverage is 100%, but the description adds no new details beyond what the schema already provides. It introduces confusion by listing 'valid' under Outputs while the input schema includes 'valid' as a property, making it ambiguous whether 'valid' is an input or output parameter.

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?

The description clearly indicates an HMAC verification operation through its title 'HMAC Verify' and the listed expectedHmac, data, key, and algorithm parameters, with a boolean 'valid' result. It is distinguishable from sibling tools like tool_hmac by the explicit 'Verify' action and output semantics.

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?

There is no guidance on when to use this tool versus alternatives such as tool_hmac or tool_hash_verify. The description lacks context about prerequisites, use cases, or situations where another tool would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools