@easynodexyz/mcp-x402

create_order

Purchase VPS or blockchain nodes with USDC on Base. Automates the x402 payment flow and returns order details with ID and status.

Instructions

Purchase a VPS or blockchain node product using USDC on Base. Handles the x402 payment flow automatically. Returns order details with ID and status.

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": {
      "productId": "<productId>",
      "period": "<period>"
    },
    "name": "create_order"
  }
}

Input Schema

Name	Required	Description
`period`	Yes	Subscription period in months
`quantity`	No	Number of instances to purchase (default: 1)
`productId`	Yes	Product ID to purchase
`customName`	No	Custom name for the instance (max 100 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Aug 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context about the currency, blockchain, and automatic payment handling, but does not mention potential side effects like charges, failure modes, or provisioning delays. This is more transparent than a bare 'create', but still incomplete.

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?

Two sentences, each earning its place. The description is front-loaded with the core purpose and adds payment/return details without fluff.

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 mutating tool with no output schema, the description provides a reasonable overview of what to expect (order ID and status). It could mention potential async behavior or failure handling, but it is sufficient for a tool of this complexity.

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 schema covers all parameters with descriptions, so the baseline is 3. The description does not add any additional semantic meaning to the parameters beyond what the schema already 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 states the tool's action: purchasing a VPS or blockchain node product via USDC on Base. It specifies the payment flow and return value, distinguishing it from sibling tools that list, get, renew, or rename instances.

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 implies this is the tool for purchasing, with context about the payment method and automatic flow. However, it does not explicitly mention when to use this over alternatives, though the sibling names make it evident this is the creation/purchase tool.

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

Deploy Server