OwlX AI Agent — Trading Intelligence

owlx_structure_read

OwlX structure-score read of a crypto symbol: 0-10 score, LONG/SHORT/WAIT direction, trigger & defense levels, confirmation checks. Free for BTC/ETH; other symbols need an OwlX Pro key (Authorization: Bearer). Educational info, not financial advice.

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

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Base symbol, e.g. BTC, SOL, WIF
`timeframe`	No	Candle timeframe (default 4h)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 18, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Disclaims educational nature and mentions authorization needs. However, with no annotations, the description misses explicit statement of read-only behavior or safety profile. Adequate but not comprehensive.

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?

Description is three sentences, front-loaded with main purpose. Each sentence adds value (purpose, auth disclaimer, educational note). No wasted words.

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?

Given no output schema, description explains return values (score, direction, levels). Covers auth constraints and use case. Could mention timeframe parameter but schema covers that.

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 parameters are already described. Description adds no extra semantic meaning for the parameters beyond what's in the schema. Baseline 3 is appropriate.

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?

Description clearly states verb ('read') and resource ('OwlX structure-score of a crypto symbol') and lists specific outputs (score, direction, levels). Does not explicitly differentiate from siblings, but the name and context make it distinct.

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

Usage Guidelines4/5

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

Provides explicit guidance on free usage for BTC/ETH and requirement of OwlX Pro key for other symbols. Does not cover when not to use this tool vs alternatives, but siblings are sufficiently different.

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

All OwlX AI Agent — Trading Intelligence tools Inspect

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

Need Help?