Draconic Market Intelligence

Ask Draconic

ask_draconic

Ask analytical questions about supported instruments, including options positioning where data is available, news context, instrument comparison, timeframe conflict, or a position or thesis the user describes. Do not call this tool for requests to place, modify or cancel orders, execute trades, stream or export raw ticks/candles, or perform unrelated tasks. Explain that limitation directly without invoking Draconic. Do not substitute a paid analysis unless the user separately requests analysis. Set market_wide=true for nse or us market and sector summaries without naming an instrument. This does not access the user's broker account or create alerts. Return the result as the authoritative Draconic card without restating it. Analysis-only Draconic market intelligence for a curated supported universe. Never buy, sell, enter, exit, or execute. Successful intelligence calls save the conversation and consume one Draconic credit. Unsupported instruments are returned clearly before charging.

Input Schema

TableJSON Schema

Name	Required	Description
`asset`	No	Alias for a single instrument when the host does not send an instruments array.
`market`	Yes	Use one of these market values: nse, us, crypto, forex, commodities. Use get_coverage to check supported instruments and timeframes. Market-wide summaries are supported only for nse and us when data is available.
`symbol`	No	Alias for a single instrument.
`chat_id`	No	For a follow-up, pass the chat_id returned by the previous Draconic response so the same conversation continues. Omit it only to start a new Draconic chat.
`question`	Yes	Any analytical question about the current market context of the requested supported instruments. Include position, comparison, timeframe, thesis, or scenario context directly in this question when relevant.
`timeframe`	No	A timeframe currently computed by Draconic.
`instrument`	No	Alias for a single instrument.
`instruments`	No	One to five supported instruments. For one instrument, asset is also accepted.
`market_wide`	No	Set true for market-wide or sector analysis in NSE/India or US. Instruments may be omitted for that request; otherwise provide one to five supported instruments.
`analysis_type`	No	Alias for timeframe.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chat_id`	Yes
`credits`	No
`analysis`	Yes
`coverage`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

changedOutput schema / properties / credits / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "credits_remaining": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "current_plan": {
+        "type": "string"
+      },
+      "free_remaining": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "plan_remaining": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "topup_remaining": {
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "credits_remaining",
+      "free_remaining",
+      "plan_remaining",
+      "topup_remaining",
+      "current_plan"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / message_ids

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": {
-        "type": "string"
-      },
-      "propertyNames": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / market / description

Previous value: -"A Draconic market family. Use get_coverage to check the actual supported instruments and timeframes. Market-wide summaries are supported only for NSE/India and US when data is available."New value: +"Use one of these market values: nse, us, crypto, forex, commodities. Use get_coverage to check supported instruments and timeframes. Market-wide summaries are supported only for nse and us when data is available."

First observedSep 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds significant behavioral context beyond annotations: it never buys/sells or accesses the broker account, does not create alerts, saves the conversation on successful calls, consumes one Draconic credit, and reports unsupported instruments before charging. This clarifies the side effects consistent with readOnlyHint=false and openWorldHint=true, with no contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and covers necessary constraints, but it is wordy and contains repetition: 'Never buy, sell, enter, exit, or execute' largely duplicates the earlier 'Do not call this tool for requests to place, modify or cancel orders, execute trades.' A tighter edit would preserve clarity while reducing redundancy.

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 complex tool with 10 parameters, an output schema, and annotations, the description is complete: it states scope, exclusions, market-wide behavior, credit consumption, conversation continuation, unsupported-instrument handling, and result formatting. Nothing an agent needs to select and invoke the tool correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying market_wide=true usage for NSE/US sector summaries without instruments, emphasizing that chat_id continues a prior Draconic chat, and instructing users to include position/thesis context in the question. This pushes it above baseline, though some parameter aliases are left to the schema.

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 opens with a specific verb and resource: 'Ask analytical questions about supported instruments.' It enumerates concrete request types (options positioning, news context, comparison, timeframe conflict, thesis) and explicitly separates itself from execution, streaming, and unrelated tasks. This clearly distinguishes it from siblings like get_coverage and get_account_usage.

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?

The description gives explicit when-to-use and when-not-to-use guidance: do not call for orders, executions, raw data streaming, or unrelated tasks; explain that limitation directly; check get_coverage for supported instruments/timeframes; set market_wide=true for NSE/US sector summaries. It is unambiguous about routing to alternatives.

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

All Draconic Market 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?