Skip to main content
Glama
Sign In
Wicked MCP server

Wicked MCP server

by WickedAPI
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

basis

Read-onlyIdempotent

Calculate spot-vs-perp basis premium and funding-implied annualized carry to evaluate basis trades. Combines Coinbase spot with Binance and Bybit perp marks.

Instructions

[Trading Data API] Spot-vs-perp basis (premium %) with funding-implied annualized carry. Spot from Coinbase; perp marks from Binance + Bybit.

Example: /v1/basis?symbol=BTC

Use when you want the spot-vs-perp premium and funding-implied annualized carry for a basis trade. Not for raw funding data (use funding_oi).

Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).

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": {
      "symbol": "<symbol>"
    },
    "name": "basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesRequired. Base crypto symbol (e.g. BTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds important context beyond annotations: pricing via x402 or API key, and that an unauthenticated request returns HTTP 402 with a decoded price in payment_required, explicitly framed as a quote rather than a failure.

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?

The description is front-loaded with the core computation, then immediately provides an example, a usage boundary, and payment behavior. Every sentence contributes to correct selection or invocation, with no wasted text.

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?

For a one-parameter, read-only trading data tool with no output schema, the description covers data sources, use case, sibling exclusion, and the important payment/402 behavior. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the symbol parameter is already documented as a required base crypto symbol. The description provides an example call and data sources but does not add further semantic meaning to the parameter itself beyond what the schema already says.

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 states a specific computation: spot-vs-perp basis (premium %) with funding-implied annualized carry, and names the exact data sources. It distinguishes the tool from the sibling funding_oi by explicitly saying it is not for raw funding data.

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?

It gives an explicit use case ('when you want the spot-vs-perp premium and funding-implied annualized carry for a basis trade') and names the alternative for raw funding data (funding_oi). No inference is required to choose between this and the sibling.

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

Deploy Server

Other Tools