Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

price

Read-onlyIdempotent

[Trading Data API] Current spot price for crypto (Coinbase) or US equities/ETFs (Alpaca SIP), via the shared routing layer.

Example: /v1/price?symbol=BTC

Use when you need the current spot price of one crypto asset or US stock/ETF. Not for history or candles (use ohlcv), or a trading view (use momentum_score or verdict).

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>",
      "class": "<class>"
    },
    "name": "price"
  }
}

Input Schema

NameRequiredDescriptionDefault
classYesOptional. stock|crypto — required for symbols outside the curated list.
symbolYesRequired. e.g. BTC, ETH, SUI, NVDA, SPY.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive. The description adds genuinely non-derivable behavior: billing via x402 (USDC on Base) or an API key, and the crucial note that an HTTP 402 is a price quote rather than a failure. It does not mention rate limits, caching/latency, or the shape of the returned price payload, which keeps it off 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 purpose and source, then example, usage/exclusions, and behavior in clearly labeled segments. Every sentence carries information; nothing is redundant with the name or annotations.

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 2-parameter read tool with full schema coverage and annotations, the description covers selection, alternatives, and auth/payment edge cases. The remaining gap is the return payload (field names, quote currency, timestamp), which matters somewhat since no output schema exists.

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%, so both parameters (symbol, class) are already documented in the schema, and the description adds only an example instance (/v1/price?symbol=BTC). It adds no extra meaning for `class` (stock|crypto) or the curated-list fallback beyond what the schema states, so the baseline 3 applies.

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 precise verb+resource (current spot price) and scopes it by asset classes with named data sources (Coinbase for crypto, Alpaca SIP for equities/ETFs). It also names the routing layer and gives a concrete example path, so an agent can distinguish it immediately from quote/history siblings.

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?

Explicitly says when to use it ('need the current spot price of one crypto asset or US stock/ETF') and when not to, naming the exact alternatives: ohlcv for history/candles and momentum_score/verdict for a trading view. Nothing is left to inference.

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

All Wicked MCP toolsInspect
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.

Resources