Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Trading Days

trading_days
Read-onlyIdempotent

Get trading days for HK, US, CN, or SG markets between two dates, providing a clear list of market open days for planning and analysis.

Instructions

Get trading days for a market between dates. market: HK/US/CN/SG.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
endYesEnd date (yyyy-mm-dd)
startYesStart date (yyyy-mm-dd)
marketYesMarket code: HK, US, CN, SG

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "half_trading_days": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "trading_days": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "trading_days",
-    "half_trading_days"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"MarketDateRangeParam"
  4. Changed5 schema fields changedv0.6.0
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `trading_days`."
    • removedOutput schema / properties / half_trading_days / description
      Removed value: -"Half-day trading sessions in the requested range (yyyy-mm-dd)."
    • removedOutput schema / properties / trading_days / description
      Removed value: -"Full trading days in the requested range (yyyy-mm-dd)."
    • removedOutput schema / title
      Removed value: -"TradingDaysResponse"
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context beyond the basic operation; it doesn't mention return format, pagination, or edge cases. With annotations covering safety, a 3 is appropriate.

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?

The description is a single, efficient sentence that front-loads the core purpose and lists valid markets. It is concise without being under-specified, though it could have included a bit more context. No unnecessary words.

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?

The tool has a simple schema, no output schema, and annotations cover safety. However, the description does not clarify the expected return format (e.g., list of date strings), whether weekends/holidays are excluded, or any date-range constraints. While not severely lacking, it leaves some ambiguity for an agent deciding whether to call it.

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 100%, so each parameter (market, start, end, _jq) is documented in the schema. The description repeats the market list (HK/US/CN/SG) but adds no additional meaning beyond the schema, such as date inclusivity or formatting details. Baseline 3 is correct since the schema does the heavy lifting.

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?

The description clearly states the tool's purpose: get trading days for a market between dates. It specifies the resource (trading days) and the scope (market and date range), and even lists valid markets. It is not a tautology and is distinguishable from siblings like trading_session, though it doesn't explicitly name alternatives.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage (when you need trading days) but provides no context about prerequisites, exclusions, or better-suited sibling tools. Given the large sibling list, explicit routing would help.

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

Deploy Server

Other Tools