HyperSignal MCP

Buy Pro (x402)

hl_buy_pro

Buy 30 days of Pro (unlimited premium calls) for $29 in USDC, paid over x402 on Base. Without an X-API-Key it issues a new Pro key; with one it renews that key (a free key is upgraded in place), adding 30 days to its current end. The first call answers with the payment requirements; pay and retry with the X-PAYMENT header. The payment is taken only once the key is ready. No automatic refunds. If the answer says the payment could not be confirmed, do not pay again: quote its reference. How to pay: https://github.com/johnsmithxy1mmm-sys/HyperliquidMCP#pricing

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tier`	Yes
`apiKey`	No
`header`	No
`renewed`	Yes
`daysAdded`	Yes
`expiresAt`	Yes
`reference`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false), the description discloses the key behavioral traits an agent needs: payment is taken only once the key is ready, no automatic refunds, and a specific remediation path when confirmation fails. This is unusually rich disclosure for a payment tool.

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 price, duration, and payment rail, then proceeds through mode selection, payment flow, and error handling. Every sentence carries operational information; nothing is redundant.

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?

Given that an output schema exists and annotations cover safety flags, the description fills the remaining gaps: payment mechanics, key lifecycle, refund policy, and failure recovery. An agent can invoke this correctly without additional context.

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?

There are zero input parameters, so the schema baseline of 4 applies. The description does not need to add parameter semantics and correctly spends its words on payment flow instead.

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: buy 30 days of Pro for $29 in USDC over x402 on Base. It explicitly distinguishes the two modes (new key vs. renewal of an existing key), which an agent can use to tell this apart from hl_request_free_key and other siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-and-how guidance: without an X-API-Key it issues a new key, with one it renews (upgrading free keys in place). It also spells out the two-step payment flow (first call returns requirements; pay and retry with X-PAYMENT) and the error path (do not pay again if confirmation fails; quote the reference).

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

All HyperSignal MCP tools Inspect

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.