Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

by com.synthexforge.x402
OverviewDiscussionsAdmin

Verify Settlement Signature

verify_settlement_signature
Read-onlyIdempotent

Free, because verifying a receipt you already paid for must never cost a second payment. use it rather than create_settlement_receipt for settlement signature, not settlement receipt; an object with detail, valid.

Input Schema

NameRequiredDescriptionDefault
bodyYesThe canonical evidenceCore from the paid response.
sha256NoThe digest to check against.
signatureNoThe Ed25519 signature (hex).

Output Schema

NameRequiredDescriptionDefault
validYesWhether the artifact verified.
detailYesHuman-readable explanation of the verdict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / detail
      Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}
    • removedOutput schema / properties / status
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / valid
      Added value: +{
+  "description": "Whether the artifact verified.",
+  "type": "boolean"
+}
    • addedOutput schema / required
      Added value: +[
+  "detail",
+  "valid"
+]
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful cost context ('Free') and explains that verification should not trigger a second payment, but does not add richer operational detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but it opens with a cost rationale instead of a purpose statement. The second sentence is run-on and includes 'an object with detail, valid', which is extraneous given the output schema.

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 a full input schema, output schema, and annotations, the description does not need to explain return values. However, it still leaves the core verification behavior and intended cryptographic check unclear, so it is only adequately complete.

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 description coverage is 100%, so body, sha256, and signature are already documented. The description does not add meaning beyond the schema, and 'an object with detail, valid' reads more like output commentary than parameter guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description mentions 'verifying a receipt you already paid for' and 'settlement signature', but never clearly states that it verifies an Ed25519 signature/digest over canonical evidenceCore. It relies on the tool name and a contrast with create_settlement_receipt rather than stating the operation directly.

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?

It explicitly names create_settlement_receipt as the alternative and says to use this tool for settlement signature rather than settlement receipt. That gives a clear sibling distinction, though it does not address conditions relative to the many other verify_* tools.

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

All Synthex Forge — x402 Paid Agent Services toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources