Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Capital Distribution

capital_distribution
Read-onlyIdempotent

Retrieve capital distribution data for a security symbol. Indicates data availability to avoid misinterpretation of zero values for indices or symbols without capital-flow data.

Instructions

Get capital distribution for a symbol. data_available is false for symbols with no capital-flow data (e.g. indices) — the other fields are still present but meaningless zeros in that case.

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.
symbolYesSecurity symbol, e.g. "700.HK". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • changedInput schema / properties / symbol / description
      Previous value: -"Security symbol, e.g. \"700.HK\""New value: +"Security symbol, e.g. \"700.HK\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "CapitalDistribution": {
-      "properties": {
-        "large": {
-          "type": "string"
-        },
-        "medium": {
-          "type": "string"
-        },
-        "small": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "large",
-        "medium",
-        "small"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "capital_in": {
-      "$ref": "#/$defs/CapitalDistribution"
-    },
-    "capital_out": {
-      "$ref": "#/$defs/CapitalDistribution"
-    },
-    "timestamp": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "timestamp",
-    "capital_in",
-    "capital_out"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed9 schema fields changedv0.6.0
    • removedOutput schema / $defs / CapitalDistribution / properties / large / description
      Removed value: -"Capital from large orders."
    • removedOutput schema / $defs / CapitalDistribution / properties / medium / description
      Removed value: -"Capital from medium orders."
    • removedOutput schema / $defs / CapitalDistribution / properties / small / description
      Removed value: -"Capital from small orders."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `capital_distribution`."
    • removedOutput schema / properties / capital_in / description
      Removed value: -"Inflow capital broken down by order size."
    • removedOutput schema / properties / capital_out / description
      Removed value: -"Outflow capital broken down by order size."
    • removedOutput schema / properties / timestamp / description
      Removed value: -"Snapshot timestamp (RFC3339)."
    • removedOutput schema / title
      Removed value: -"CapitalDistributionResponse"
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable nuance: for symbols without capital-flow data, data_available is false and other fields are present but meaningless zeros. This goes beyond the annotation safety profile and helps the agent interpret results correctly.

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, focused sentence that states the purpose and the key caveat about data_available. It is concise and front-loaded with the primary action. It could be slightly better structured by separating the purpose from the edge-case note, but it is efficient.

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 the tool's simplicity, no output schema, and rich annotations, the description covers the essential behavioral quirk (data_available and meaningless zeros) and the parameter caveat. It is complete enough for an agent to invoke correctly, though it could mention the return format or typical use cases, which are minor omissions.

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 description coverage is 100%, so the schema documents both parameters. The description adds critical detail for the symbol parameter: padded codes like '00700.HK' return an empty record instead of an error, and canonical form is required. This enriches the schema's basic description and is important for correct invocation.

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 states a clear purpose: 'Get capital distribution for a symbol.' It names the resource and action, but does not differentiate from the sibling tool 'capital_flow', which is a potential alternative for similar data. This prevents a top score because the agent must infer which tool is appropriate.

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

Usage Guidelines3/5

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

The description provides a context clue about data_available being false for symbols without capital-flow data, which hints at when the tool may not be useful. However, it does not explicitly state when to use this tool versus alternatives like capital_flow, nor does it give any exclusion criteria. This is a moderate gap.

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