Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

momentum_score

Read-onlyIdempotent

[Trading Data API] Alias of /v1/verdict. Multi-asset momentum verdict (bias, confidence, thesis, entry/invalidation/targets, signal readings) from the oracle.py pipeline, run on a separate Python service. Scoped to 10 assets.

Example: /v1/momentum-score?symbol=BTC&timeframe=1h

Use when you want a ready-made LONG/SHORT/NEUTRAL view with confidence, thesis and entry/invalidation/targets for a supported asset. Not for raw inputs (use price, atr, funding_oi). Same data as verdict, which is the newer name.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesRequired. One of: BTC, ETH, SOL, SUI, NVDA, IBIT, COIN, QQQ, TQQQ, DIA.
timeframeNoOptional. 15m, 1h, 4h, 1D, 1W (default 1h).

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/non-destructive, and the description adds genuinely non-obvious context: pricing via x402 (USDC on Base) or an API key, and that a bare HTTP 402 carries a price quote rather than being a failure. That last point is a real operational trap avoided. Slight deduction because it doesn't say whether the oracle pipeline can go stale or fail independently.

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?

Front-loaded with identity and payload, then example, usage, and behavior. Mostly tight, but 'Alias of /v1/verdict' and 'Same data as verdict, which is the newer name' are redundant statements of the same fact.

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?

No output schema exists, and the description compensates by enumerating the returned fields (bias, confidence, thesis, entry/invalidation/targets, signal readings). It also covers the payment/discovery path and the 10-asset boundary, leaving nothing an agent needs to call it correctly.

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% (symbol enum and timeframe values fully documented in-schema), so the schema carries the semantics. The description reinforces the 10-asset scope and shows a sample query string, but adds no format or default detail 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?

States the concrete resource (multi-asset momentum verdict) and enumerates its payload (bias, confidence, thesis, entry/invalidation/targets, signal readings), plus the source pipeline and 10-asset scope. It also explicitly positions itself against siblings: it is the same data as verdict (the newer name) and is not for raw inputs like price/atr/funding_oi.

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 an explicit when-to-use ('ready-made LONG/SHORT/NEUTRAL view with confidence, thesis and entry/invalidation/targets') and an explicit when-not ('Not for raw inputs') naming the three alternative tools. It also flags that verdict is the newer name for the same data, which is exactly the routing decision an agent needs.

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