Skip to main content
Glama
FractalAI MCP Server

FractalAI MCP Server

by johnInarti

Get x402 payment requirements

x402_checkout

Returns live x402 payment requirements—price, network, USDC asset, payTo address, and accepts entries—for a paid FractalAI resource so you know how much and how to pay before signing.

Instructions

Return the live x402 (HTTP 402) payment requirements for a paid FractalAI resource: price, network, USDC asset, payTo address and the accepts[] entries (EIP-3009 gasless and txHash fallback). Free — it never moves funds. Use it before pqc_sign / seal_provenance / attest_decision to learn exactly how much and how to pay. Pass resource='manifest' for the full .well-known/x402.json.

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": {
      "resource": "<resource>"
    },
    "name": "x402_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesWhich paid resource to price, or 'manifest' for the whole x402 manifest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does disclose the safety profile ('Free — it never moves funds') plus that the values are 'live' rather than cached. It also characterizes the two payment paths in accepts[] (EIP-3009 gasless vs txHash fallback) and what the manifest enum value returns. It omits auth requirements, rate limits, and caching semantics, which keeps it short of a 5.

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?

Front-loaded with the verb and payload, then the cost/safety note, then the usage ordering, then the parameter hint — a sensible priority order. Every clause earns its place and nothing is repeated from the schema.

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?

For a one-parameter read tool with no annotations and no output schema, the description supplies what matters: what is returned, that it is free and non-mutating, and when to call it. Remaining gaps (auth, rate limits, error behavior for an unknown resource) are minor for a pricing lookup.

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% and the single enum parameter is already documented, so the baseline would be 3. The description adds value on top by explaining that resource='manifest' returns the full .well-known/x402.json, i.e. it describes the consequence of that enum choice rather than just restating it.

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?

States a specific verb and resource ('Return the live x402 ... payment requirements') and enumerates the payload fields (price, network, USDC asset, payTo, accepts[] entries), so an agent knows exactly what comes back. The sibling names pqc_sign / seal_provenance / attest_decision make clear this is the pricing prerequisite, not a payment or signing operation.

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?

Gives explicit sequencing guidance: call this before pqc_sign / seal_provenance / attest_decision to learn how much and how to pay. It does not state a when-not condition or whether the paid siblings themselves return 402 and force a retry, but the intended call order is unambiguous.

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