mcp-livedatapro

getTradingHalts

Live stock market circuit breaker triggers, LULD (Limit Up-Limit Down) halts, and pending regulatory trading resumptions. Use when monitoring live stock exchange regulatory trading halts, LULD (Limit Up-Limit Down) volatility pauses, halt reason codes (T1, T2, LULD), and expected resumption timestamps. Do not use for standard stock closing prices (use getStockEodPrices).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getTradingHalts"
  }
}

Input Schema

Name	Required	Description	Default
`exchange`	No	Stock exchange code filter (defaults to 'ALL' for all major global venues).	ALL

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / exchange / default
```
Added value: +"ALL"
```
- addedInput schema / properties / exchange / enum
```
Added value: +[
+  "ALL",
+  "NYSE",
+  "NASDAQ",
+  "AMEX",
+  "LSE",
+  "XETRA"
+]
```
- addedInput schema / properties / exchange / examples
```
Added value: +[
+  "NASDAQ"
+]
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / exchange / description

Previous value: -"Stock exchange filter (e.g., NYSE, NASDAQ, LSE)"New value: +"Stock exchange code filter (defaults to 'ALL' for all major global venues)."

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose important traits: the data is live/real-time, it covers pending resumptions rather than settled history, and it exposes reason-code semantics. It omits operational traits such as refresh cadence, whether any historical halts are returned, and response shape, which keeps it short of a 5 for an unannotated tool.

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?

Three sentences, front-loaded with the resource and followed by usage routing; every sentence serves a purpose. Minor waste in expanding 'LULD (Limit Up-Limit Down)' twice and repeating the halt vocabulary between sentence one and two.

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?

No output schema and no annotations, but the description enumerates the returned content (halt types, reason codes, expected resumption times), which is what an agent needs for a single-optional-param read tool. Missing only freshness semantics (polling expectations) and return structure hints.

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?

Only one parameter (exchange) and schema description coverage is 100%, including an enum and a default, so the schema fully documents it. The description says nothing about exchange filtering or that 'ALL' is the default, adding no meaning beyond the schema — the baseline 3 applies.

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 specific resource and data domain: live circuit breaker triggers, LULD halts, and pending regulatory resumptions, plus the concrete payload of reason codes (T1, T2, LULD) and resumption timestamps. It explicitly names the sibling it is not (getStockEodPrices), so an agent can separate it from closing-price tools without opening a schema.

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?

Explicit 'Use when monitoring live stock exchange regulatory trading halts...' condition, followed by an explicit 'Do not use for standard stock closing prices (use getStockEodPrices)' exclusion that routes to the named alternative. This is the when/when-not/alternative pattern in full.

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

All mcp-livedatapro 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?