Skip to main content
Glama
FTHTrading

Genesis402

by FTHTrading
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Issue a signed Ed25519 receipt that binds your SHA-256 diges

genesis402_prove

Issue a paid, signed Ed25519 receipt binding your SHA-256 digest or text and an optional claim to a settled payment and timestamp. Verify offline as a timestamped proof you held a document.

Instructions

Paid (price from the live 402 quote). Issue a signed Ed25519 receipt that binds your SHA-256 digest (or text, which is hashed for you) and an optional claim to a settled payment and timestamp. Use as a cheap timestamped proof that you held a document or statement. Give sha256 or text. The receipt signature verifies offline; the receipt chain is not externally anchored on-chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoRaw text to hash and prove, up to 16,384 characters. Provide this or sha256.
claimNoOptional short statement bound into the receipt, e.g. 'Draft v2 of the purchase agreement'.
sha256NoLowercase hex SHA-256 digest (64 characters) of the content to prove. Provide this or text.
payment_signatureNoOptional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.2
    • addedInput schema / properties / claim / description
      Added value: +"Optional short statement bound into the receipt, e.g. 'Draft v2 of the purchase agreement'."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."
    • addedInput schema / properties / sha256 / description
      Added value: +"Lowercase hex SHA-256 digest (64 characters) of the content to prove. Provide this or text."
    • addedInput schema / properties / text / description
      Added value: +"Raw text to hash and prove, up to 16,384 characters. Provide this or sha256."
  2. First observedv0.3.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint=false annotation, the description discloses the paid nature ('Paid (price from the live 402 quote)'), offline verifiability of the signature, and that the receipt chain is not externally anchored on-chain. This is meaningful behavioral context with no contradiction to annotations.

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 three short sentences with no filler. Payment and core action are front-loaded, and each sentence adds distinct information: what it issues, when to use it, and how verification behaves.

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?

Despite lacking an output schema, the description covers purpose, input options, payment behavior, and offline verification. It does not describe the exact response shape, but an agent has enough context to invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by noting that text 'is hashed for you,' implying sha256/text mutual exclusivity, and by clarifying the quote/payment flow. These hints go beyond the schema's individual parameter descriptions.

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 names a specific operation—'Issue a signed Ed25519 receipt'—and the resources involved (SHA-256 digest/text, optional claim, payment, timestamp). It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools like genesis402_receipt, so it stops short of a 5.

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 provides a clear use case: 'Use as a cheap timestamped proof that you held a document or statement.' It also tells the caller to 'Give sha256 or text.' However, it does not explicitly state when not to use this tool or mention alternatives, so it lacks full exclusion guidance.

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