DAMO Market State

Get DAMO market state for several symbols

get_market_states

Read-onlyIdempotent

Use when the user asks about several crypto assets at once. Same as get_market_state for up to 50 symbols in one call.

Input Schema

Name	Required	Description	Default
`layer`	No	verified = closed candles (recorded, never changed); live = forming candles (provisional)	verified
`proof`	No	Also put DAMO's Ed25519 signature in the result body as 'proof'.
`format`	No	compact = symbol, layer, time, vector, short citation and remaining quota only. full = per-timeframe state, seq, hash and engine version (for citing and checking).	full
`symbols`	Yes
`timeframes`	No	Optional. Only these timeframes are returned and counted against the quota (case-sensitive: 1m = minute, 1M = month). Omit for all 10.

Output Schema

Name	Required	Description	Default
`count`	No
`layer`	Yes
`proof`	No
`quota`	No
`errors`	No
`results`	Yes
`citation`	No
`quota_remaining`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / symbols / items / description

Previous value: -"Symbol, e.g. BTCUSDT (Binance USDⓈ-M perpetual naming)"New value: +"Ticker, e.g. BTCUSDT. BTC, btc, BTC/USDT, BTC-PERP and coin names like Bitcoin are also accepted. Not a sentence: on a wrong symbol the error lists did_you_mean."

addedInput schema / properties / symbols / items / maxLength
```
Added value: +40
```

Changed2 schema fields changedOct 16, 2026

changedOutput schema / properties / results / items / properties / as_of / description

Previous value: -"verified: time of the latest closed candle (UTC)"New value: +"verified: when DAMO last wrote this record (UTC). Each timeframe's own close time is states[tf].candle_close"

changedOutput schema / properties / results / items / properties / observed_at / description

Previous value: -"live: observation time (UTC)"New value: +"live: when DAMO observed the forming candles (UTC)"

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "citation": {
+      "type": "string"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "errors": {
+      "items": {
+        "properties": {
+          "error": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          },
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "layer": {
+      "enum": [
+        "verified",
+        "live"
+      ],
+      "type": "string"
+    },
+    "proof": {
+      "type": "object"
+    },
+    "quota": {
+      "type": "object"
+    },
+    "quota_remaining": {
+      "type": "integer"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "as_of": {
+            "description": "verified: time of the latest closed candle (UTC)",
+            "type": "string"
+          },
+          "chain_head": {
+            "type": "object"
+          },
+          "citation": {
+            "type": "string"
+          },
+          "engine_version": {
+            "type": "string"
+          },
+          "layer": {
+            "enum": [
+              "verified",
+              "live"
+            ],
+            "type": "string"
+          },
+          "observed_at": {
+            "description": "live: observation time (UTC)",
+            "type": "string"
+          },
+          "proof": {
+            "description": "Ed25519 signature when proof=true",
+            "type": "object"
+          },
+          "quota": {
+            "type": "object"
+          },
+          "quota_remaining": {
+            "type": "integer"
+          },
+          "stale": {
+            "type": "boolean"
+          },
+          "states": {
+            "additionalProperties": {
+              "type": "object"
+            },
+            "description": "full format: per-timeframe state, code, candle status and record fields",
+            "type": "object"
+          },
+          "symbol": {
+            "type": "string"
+          },
+          "vector": {
+            "description": "State codes in timeframe order (1 bull_momentum, 2 weakening, 3 bear_momentum, 4 recovery); null = not requested or not available",
+            "items": {
+              "maximum": 4,
+              "minimum": 1,
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "type": "array"
+          },
+          "vector_order": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "symbol",
+          "layer",
+          "vector"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "layer",
+    "results"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / format

Added value: +{
+  "default": "full",
+  "description": "compact = symbol, layer, time, vector, short citation and remaining quota only. full = per-timeframe state, seq, hash and engine version (for citing and checking).",
+  "enum": [
+    "full",
+    "compact"
+  ],
+  "type": "string"
+}

addedInput schema / properties / proof

Added value: +{
+  "default": false,
+  "description": "Also put DAMO's Ed25519 signature in the result body as 'proof'.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / timeframes

Added value: +{
+  "description": "Optional. Only these timeframes are returned and counted against the quota (case-sensitive: 1m = minute, 1M = month). Omit for all 10.",
+  "items": {
+    "enum": [
+      "1m",
+      "5m",
+      "15m",
+      "1h",
+      "4h",
+      "12h",
+      "1d",
+      "3d",
+      "1w",
+      "1M"
+    ],
+    "type": "string"
+  },
+  "type": "array",
+  "uniqueItems": true
+}

First observedOct 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The only real addition is the claim of behavioral equivalence to get_market_state, plus the 50-symbol cap (which repeats maxItems from the schema). Nothing is said about quota consumption per symbol, partial failures across a batch, or whether the whole call fails if one symbol is bad — meaningful gaps for a batch tool whose schema notes a per-timeframe quota.

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?

Two sentences, front-loaded with the triggering situation and then the equivalence and batch limit. Every clause earns its place and there is no filler.

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?

Output schema exists and annotations are rich, so return values and safety need no explanation. However, the description defines the tool entirely by reference to get_market_state, forcing the agent to read another definition to understand the response shape, and it omits batch-specific behavior (per-symbol quota cost, mixed valid/invalid symbol handling) that matters at 50 items.

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 80%, so the schema already explains layer, proof, format, symbols (with accepted ticker variants and did_you_mean errors) and timeframes quota accounting. The description adds no parameter-level meaning beyond the 50-symbol limit already encoded as maxItems, so baseline 3 applies.

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?

States a clear capability: batch retrieval of DAMO market state for several crypto assets, up to 50 per call. It explicitly ties itself to the sibling get_market_state as the multi-symbol form, so an agent can distinguish it from the single-symbol tool. No verb is spelled out, but 'Same as get_market_state ... in one call' makes the resource and operation unambiguous.

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?

'Use when the user asks about several crypto assets at once' gives a clear selection condition, and 'Same as get_market_state for up to 50 symbols' implicitly routes single-symbol requests to the sibling. It stops short of any explicit exclusion or mention of list_symbols/get_state_definitions, so the routing picture is not fully closed.

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

All DAMO Market State 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?