Skip to main content
Glama
FractalAI MCP Server

FractalAI MCP Server

by johnInarti

Buy a post-quantum signature

pqc_sign

Signs a message's SHA-256 digest or a hex hash with a post-quantum ML-DSA-65 key after a $0.02 USDC x402 payment, returning digest, signature, public key, and payment details.

Instructions

Pay $0.02 USDC (x402) for one post-quantum ML-DSA-65 / Dilithium-3 (NIST FIPS 204) signature over your message (its sha256 is signed) or a hex hash (signed directly). Returns { digest, signature, public_key, payment }. Without payment_tx_hash you get the payment challenge, not a signature. The signature proves these exact bytes were signed by this server's PQC key — nothing about their truthfulness, and 'quantum-resistant per NIST' is not 'unbreakable'.

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": "pqc_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashNoHex digest signed directly. Provide message OR hash.
payerNoOptional payer address hint.
messageNoUTF-8 string; sha256(message) is signed.
payment_tx_hashNoA confirmed USDC-on-Base transaction hash paying the required amount to the treasury. If omitted, the tool returns the x402 payment challenge (accepts[]) instead of a result — pay first, then call again with this set. One txHash buys exactly one call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior5/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 and meets it: it discloses cost ($0.02 USDC), the payment gating behavior, that one txHash buys exactly one call, and that an unpaid call returns a challenge rather than a signature. It also bounds what the result proves (these exact bytes were signed by this key) and disclaims 'NIST quantum-resistant' as 'unbreakable', which is exactly the caveat an agent needs before citing the output.

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?

Content is front-loaded, starting with price and algorithm before the input rule and the return shape. Three sentences carry cost, inputs, two-step payment flow, return fields, and a scope disclaimer with little waste, though the caveat sentence is dense and slightly crowds the operational content.

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?

There is no output schema, but the description enumerates the returned fields ({ digest, signature, public_key, payment }) and describes the no-payment failure mode. For a 4-parameter, no-annotation tool with a paid two-step flow, nothing material is missing for correct invocation.

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%, and the schema already explains message (sha256 signed), hash (signed directly), payer hint, and the payment_tx_hash challenge flow. The description restates the message/hash distinction and the payment behavior but adds no new syntax, format, or constraint beyond what the schema already documents, so the baseline of 3 applies.

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 names a specific action (pay for one post-quantum ML-DSA-65 / Dilithium-3 signature over a message or hex hash) with the algorithm, standard (NIST FIPS 204), and price. That is concrete enough that an agent can distinguish it from verify_proof or attest_decision without opening any sibling schema.

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 gives the operational rule: call without payment_tx_hash to receive the x402 challenge, pay, then call again with the hash. It also states message vs hash as mutually exclusive inputs. It does not explicitly point to x402_checkout as the payment path, so the routing guidance stops one step short of a 5.

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