Skip to main content
Glama
SAP MultiHopper Mandate Vault MCP Server

SAP MultiHopper Mandate Vault MCP Server

by LBCron

multihopper_verify_webhook

Verify x-multihopper-signature HMAC-SHA256 webhook payloads in constant time to authenticate incoming requests and reject tampered payloads.

Instructions

Verifies x-multihopper-signature HMAC-SHA256 webhook payload in constant time.

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": {
      "rawBody": "<rawBody>",
      "signatureHex": "<signatureHex>",
      "secret": "<secret>"
    },
    "name": "multihopper_verify_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
secretYes
rawBodyYes
signatureHexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully flags constant-time comparison (timing-attack resistance), but never says what happens on mismatch — whether it returns a boolean, throws, or returns an error object — nor that a failed check should block further processing. For a security-critical primitive with zero annotation coverage, that is a material gap.

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?

A single front-loaded sentence with no filler; the algorithm, header name, and constant-time property are all packed in without redundancy. Nothing in it is wasted, though the terseness leaves the gaps noted in other dimensions.

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?

With no output schema, no annotations, and three undocumented parameters, the description should at minimum state the return contract (boolean vs. thrown error) and the raw-body requirement. It conveys the core operation but omits both, leaving an agent able to guess the call but not the handling of the result.

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 description coverage is 0% across all three required parameters, so the description must compensate and does not. It never explains that rawBody must be the unparsed raw request body bytes (a common and silent failure mode), that signatureHex is the hex-decoded value of the header, or that secret is the shared signing 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 (verifies) and resource (x-multihopper-signature HMAC-SHA256 webhook payload), plus the algorithm and constant-time property, which is enough to distinguish it from the listed siblings (fee quotes, program verification, mandate encoding, hierarchy derivation). It stops short of saying what a verification outcome looks like, but the operation itself is unambiguous.

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 call this versus other validation steps, no statement of prerequisites (e.g. that the payload must be captured before JSON parsing so the exact bytes are preserved), and no note on which side of a webhook handler this belongs. An agent must infer the entire calling context from the single sentence.

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