Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Verify Webhook Signature

lexware_verify_webhook_signature
Read-onlyIdempotent

Verify Lexware webhook signatures by comparing the X-Lxo-Signature header against the raw request body, confirming authenticity via RSA-SHA512 and the official public key.

Instructions

Verify a Lexware webhook X-Lxo-Signature (RSA-SHA512, base64) against the raw request body. Pass the EXACT raw HTTP body bytes you received — do not JSON.parse/stringify round-trip, as Lexware signs the compact JSON as transmitted (whitespace and key order matter). On first call the public key is fetched once from developers.lexware.io and cached for the process lifetime; set LEXWARE_WEBHOOK_PUBLIC_KEY (PEM) to override (recommended for production where you cannot tolerate one-time TLS-substitution risk on the public-key fetch).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payloadYesRaw HTTP request body received from Lexware (verbatim, untransformed).
signatureYesValue of the X-Lxo-Signature header (base64).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description goes beyond by detailing the public key retrieval and caching mechanism, the option to override with an environment variable for production, and the critical warning about not modifying the request body. These details add significant behavioral context.

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?

The description is exceptionally concise, consisting of two sentences that cover purpose, usage instructions, behavioral details, and production considerations without any redundant information.

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?

Given that the tool has no output schema and the input schema is fully covered, the description provides all necessary context: the verification algorithm, handling of the body, caching behavior, and production override. It is complete for an agent to understand and use the tool correctly.

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?

The input schema already has 100% coverage with clear descriptions for both parameters (payload and signature). The description repeats the warning about not transforming the payload, which adds some emphasis but not new semantic information beyond what the schema provides.

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?

The description clearly specifies the tool's function: verifying a Lexware webhook signature using RSA-SHA512. It identifies the exact header and algorithm, and distinctively separates this security tool from the numerous CRUD sibling tools.

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?

The description provides explicit instructions on how to use the tool: pass the exact raw body bytes, avoid JSON transformations. It also explains caching behavior and the override environment variable. However, it does not explicitly mention when not to use this tool or alternatives, though the uniqueness of the tool makes this less critical.

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