Skip to main content
Glama
Sign In

MorseByte x402 Edge Data Refinery & Quant Gateway

by io.github.Ceejaythenerd
OverviewDiscussionsAdmin

Quantitative Market Regime Classifier

morsebyte_quant_regime
Read-onlyIdempotent

Compute RSI-14, EMA-20/50, volatility, lag-1 autocorrelation, and market regime ($0.050 USDC via x402).

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": {
      "closes": "<closes>"
    },
    "name": "morsebyte_quant_regime"
  }
}

Input Schema

NameRequiredDescriptionDefault
closesYesAt least 10 closing prices
symbolNo
timeframeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / closes / description
      Previous value: -"Array of at least 10 closing prices"New value: +"At least 10 closing prices"
    • removedInput schema / properties / symbol / description
      Removed value: -"Ticker symbol (e.g. BTC-USD)"
    • removedInput schema / properties / timeframe / description
      Removed value: -"Candle timeframe (e.g. 1h, 1d)"
  2. Changed10 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / closes / description
      Previous value: -"Array of chronological closing prices (minimum 30 candles required for accurate EMA/RSI calculation)"New value: +"Array of at least 10 closing prices"
    • removedInput schema / properties / closes / items / description
      Removed value: -"Closing price for candle period"
    • removedInput schema / properties / closes / maxItems
      Removed value: -500
    • removedInput schema / properties / closes / minItems
      Removed value: -30
    • removedInput schema / properties / closes / title
      Removed value: -"Chronological Closing Prices"
    • changedInput schema / properties / symbol / description
      Previous value: -"Optional asset ticker identifier (e.g. BTCUSD, XAUUSD, V75)"New value: +"Ticker symbol (e.g. BTC-USD)"
    • removedInput schema / properties / symbol / title
      Removed value: -"Asset Ticker Symbol"
    • addedInput schema / properties / timeframe
      Added value: +{
+  "description": "Candle timeframe (e.g. 1h, 1d)",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "classification": {
-      "description": "Regime and risk classification output",
-      "properties": {
-        "market_regime": {
-          "description": "MOMENTUM_BREAKOUT, MEAN_REVERTING, or RANDOM_WALK_CHOP",
-          "type": "string"
-        },
-        "recommended_risk_fraction": {
-          "description": "Suggested position risk fraction (e.g. 0.015)",
-          "type": "number"
-        },
-        "trend_structure": {
-          "description": "BULLISH_TREND, BEARISH_TREND, or CONSOLIDATION",
-          "type": "string"
-        }
-      },
-      "required": [
-        "trend_structure",
-        "market_regime",
-        "recommended_risk_fraction"
-      ],
-      "type": "object"
-    },
-    "indicators": {
-      "description": "Computed technical indicators",
-      "properties": {
-        "ema_20": {
-          "description": "20-period Exponential Moving Average",
-          "type": "number"
-        },
-        "ema_50": {
-          "description": "50-period Exponential Moving Average",
-          "type": "number"
-        },
-        "lag1_autocorrelation": {
-          "description": "Lag-1 serial correlation of log returns",
-          "type": "number"
-        },
-        "period_volatility_pct": {
-          "description": "Log-return standard deviation percentage",
-          "type": "number"
-        },
-        "rsi_14": {
-          "description": "14-period Relative Strength Index",
-          "type": "number"
-        }
-      },
-      "required": [
-        "rsi_14",
-        "ema_20",
-        "ema_50",
-        "period_volatility_pct",
-        "lag1_autocorrelation"
-      ],
-      "type": "object"
-    },
-    "last_price": {
-      "description": "Most recent closing price",
-      "type": "number"
-    },
-    "provider": {
-      "description": "Service provider name",
-      "type": "string"
-    },
-    "sample_size": {
-      "description": "Number of closing prices analyzed",
-      "type": "number"
-    },
-    "symbol": {
-      "description": "Evaluated ticker symbol",
-      "type": "string"
-    }
-  },
-  "required": [
-    "provider",
-    "symbol",
-    "sample_size",
-    "last_price",
-    "indicators",
-    "classification"
-  ],
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds a genuinely non-obvious behavioral trait: the tool is paid, costing $0.050 USDC via x402, which an agent must know before calling. It omits failure modes and the minimum-data behavior, but the payment disclosure is a real value-add.

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?

A single dense sentence that front-loads the verb and the computed outputs, with the cost appended. No filler, no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 usefully enumerates the returned indicators, and the schema carries the minimum-length constraint. However, for a 3-parameter tool at 33% schema coverage, it leaves 'symbol' and 'timeframe' entirely undefined and never explains what values 'market regime' can take.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — 'closes' is documented ('At least 10 closing prices') but 'symbol' and 'timeframe' have no schema descriptions. The description mentions neither of them, so it fails to compensate for the coverage gap: an agent gets no format hints (e.g., '1h', 'BTCUSDT') or meaning for those two parameters.

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?

Specific verb ('Compute') paired with an explicit enumeration of the outputs (RSI-14, EMA-20/50, volatility, lag-1 autocorrelation, market regime), so the agent knows exactly what the tool produces. No sibling overlaps in domain (content digest, DOM snapshot, link verification), so no differentiation burden exists.

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

Usage Guidelines2/5

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

The description gives no when-to-use, when-not-to-use, or alternative-tool guidance. The only usage-adjacent signal is the cost disclosure ('$0.050 USDC via x402'), which helps an agent weigh invocation but does not tell it when this tool is the right choice.

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

All MorseByte x402 Edge Data Refinery & Quant Gateway 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