Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Fund Holders

fund_holder
Read-onlyIdempotent

Find funds and ETFs that hold a specific security symbol, such as a stock or ETF, to identify its institutional and fund ownership.

Instructions

Get funds and ETFs that hold a given symbol.

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": {
-    "FundHolderItem": {
-      "properties": {
-        "change": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "fund_name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "fund_symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "ratio": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "reported_at": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "shares": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "fund_holders": {
-      "items": {
-        "$ref": "#/$defs/FundHolderItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"SymbolParam"
  4. Changed11 schema fields changedv0.6.0
    • removedOutput schema / $defs / FundHolderItem / description
      Removed value: -"One holder in `fund_holder`'s `fund_holders`.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / $defs / FundHolderItem / properties / change / description
      Removed value: -"Change in shares."
    • removedOutput schema / $defs / FundHolderItem / properties / fund_name / description
      Removed value: -"Fund name."
    • removedOutput schema / $defs / FundHolderItem / properties / fund_symbol / description
      Removed value: -"Fund symbol."
    • removedOutput schema / $defs / FundHolderItem / properties / ratio / description
      Removed value: -"Ownership ratio."
    • removedOutput schema / $defs / FundHolderItem / properties / reported_at / description
      Removed value: -"Report date."
    • removedOutput schema / $defs / FundHolderItem / properties / shares / description
      Removed value: -"Shares held."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `fund_holder`. Wraps a `fund_holders` array.\n\nSubset of documented fields; upstream may return more."
    • removedOutput schema / properties / fund_holders / description
      Removed value: -"Funds / ETFs that hold the symbol."
    • removedOutput schema / title
      Removed value: -"FundHolderResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "FundHolderItem": {
+      "description": "One holder in `fund_holder`'s `fund_holders`.\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "change": {
+          "description": "Change in shares.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "fund_name": {
+          "description": "Fund name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "fund_symbol": {
+          "description": "Fund symbol.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ratio": {
+          "description": "Ownership ratio.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reported_at": {
+          "description": "Report date.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "shares": {
+          "description": "Shares held.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `fund_holder`. Wraps a `fund_holders` array.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "fund_holders": {
+      "description": "Funds / ETFs that hold the symbol.",
+      "items": {
+        "$ref": "#/$defs/FundHolderItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "FundHolderResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. First observedv0.1.12

TDQS

B3.4/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, so the agent knows this is a safe read operation. The description adds no further behavioral context such as rate limits, authentication needs, or edge-case behavior beyond what the schema parameter notes provide. It does not contradict the annotations, but adds minimal value.

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?

The description is a single, succinct sentence with zero filler. It is front-loaded with the core action and resource, making it easy to scan. Every word earns its place.

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, full schema coverage, and strong annotations, the description is largely sufficient. It states the output purpose implicitly (returning funds/ETFs that hold the symbol). No output schema exists, but for a simple lookup, the description covers the essential context. Minor gaps like pagination or limits are not critical here.

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%, with both parameters (symbol and _jq) documented. The symbol parameter already includes a useful note about canonical form. The description itself does not elaborate on parameter meanings, but the schema fully covers them, so the baseline of 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?

The description clearly states the verb 'get' and the resource 'funds and ETFs that hold a given symbol'. It is specific and understandable, though it does not explicitly name sibling tools like fund_positions to differentiate itself. The purpose is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It simply states the function without contextual routing, leaving the agent to infer applicability from the name and schema.

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