Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

Spot vs Perpetual Cash-and-Carry Basis Scanner

verifystack_spot_perp_basis
Read-onlyIdempotent

Scan cross-exchange spot-vs-perpetual basis, executable BBO spreads, and combined 30-day carry APR across Gate.io, OKX, and Hyperliquid to identify cash-and-carry opportunities.

Instructions

Paid x402 API ($0.008 USDC on Base): Live cross-exchange cash-and-carry Spot vs Perpetual basis, executable BBO spread, and combined 30d carry APR scanner across Gate.io, OKX, and Hyperliquid.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax opportunities returned (1-100, default 15)
symbolNoOptional asset ticker filter (e.g. BTC, ETH, SOL)
minBasisBpsNoMinimum absolute executable basis spread in bps (0-5000)
notionalUsdNoOptional position size in USD to estimate 30d carry return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so safety is covered. The description adds genuinely valuable behavior beyond annotations: this is a paid x402 endpoint costing $0.008 USDC on Base, and data is live across three named venues. It does not disclose pagination, rate limits, or what happens if payment/limits fail, so it earns a solid but not exceptional score.

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?

A single packed sentence with no filler; the most decision-relevant fact (it is a paid API with a stated price) is front-loaded. Slightly dense with parallel noun phrases, but every clause carries information.

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?

With no output schema, the description carries the burden of explaining return content and does so by listing basis, executable BBO spread, and 30d carry APR across three venues. Combined with full schema coverage and write-safety annotations, remaining gaps (output shape, error behavior) are minor for a read-only scanner.

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%, including ranges and defaults for limit, symbol, minBasisBps, and notionalUsd, so the baseline is 3. The description does add conceptual framing — 'executable BBO spread' ties to minBasisBps and 'combined 30d carry APR' ties to notionalUsd — but no syntax or unit clarification beyond the schema.

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 resource and verb ('Live cross-exchange cash-and-carry Spot vs Perpetual basis... scanner') and enumerates its outputs (executable BBO spread, 30d carry APR) plus the covered venues (Gate.io, OKX, Hyperliquid). An agent can tell what it produces, though it does not explicitly distinguish itself from the sibling verifystack_live_funding_arb.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'cash-and-carry Spot vs Perpetual basis' — an agent can infer this is for basis/carry opportunities, but there is no explicit when-to-use versus when-not, and no named alternative such as the funding-arb sibling. The 'executable' qualifier hints at tradability checks but is not framed as guidance.

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