Skip to main content
Glama
longbridge

longbridge

Official

Fund Positions

fund_positions
Read-onlyIdempotent

Get current fund positions. counter_id is the fund id (e.g. UT/FD/HK0000384492); its last /-separated segment is the ISIN.

Instructions

Get current fund positions. counter_id is the fund id (e.g. UT/FD/HK0000384492); its last /-separated segment is the ISIN.

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.

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: -{
      -  "$defs": {
      -    "FundPosition": {
      -      "properties": {
      -        "cost_net_asset_value": {
      -          "type": "string"
      -        },
      -        "currency": {
      -          "type": "string"
      -        },
      -        "current_net_asset_value": {
      -          "type": "string"
      -        },
      -        "holding_units": {
      -          "type": "string"
      -        },
      -        "net_asset_value_day": {
      -          "type": "string"
      -        },
      -        "symbol": {
      -          "type": "string"
      -        },
      -        "symbol_name": {
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "symbol",
      -        "symbol_name",
      -        "currency",
      -        "holding_units",
      -        "current_net_asset_value",
      -        "net_asset_value_day",
      -        "cost_net_asset_value"
      -      ],
      -      "type": "object"
      -    },
      -    "FundPositionChannel": {
      -      "properties": {
      -        "account_channel": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "fund_info": {
      -          "items": {
      -            "$ref": "#/$defs/FundPosition"
      -          },
      -          "type": "array"
      -        }
      -      },
      -      "required": [
      -        "fund_info"
      -      ],
      -      "type": "object"
      -    }
      -  },
      -  "properties": {
      -    "list": {
      -      "items": {
      -        "$ref": "#/$defs/FundPositionChannel"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "list"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. Changed12 schema fields changedv0.6.0
    • removedOutput schema / $defs / FundPosition / properties / cost_net_asset_value / description
      Removed value: -"Cost net asset value."
    • removedOutput schema / $defs / FundPosition / properties / currency / description
      Removed value: -"Settlement currency."
    • removedOutput schema / $defs / FundPosition / properties / current_net_asset_value / description
      Removed value: -"Net asset value at last settlement."
    • removedOutput schema / $defs / FundPosition / properties / holding_units / description
      Removed value: -"Number of fund units held."
    • removedOutput schema / $defs / FundPosition / properties / net_asset_value_day / description
      Removed value: -"Settlement timestamp (RFC3339)."
    • removedOutput schema / $defs / FundPosition / properties / symbol / description
      Removed value: -"Fund ISIN code."
    • removedOutput schema / $defs / FundPosition / properties / symbol_name / description
      Removed value: -"Display name of the fund."
    • removedOutput schema / $defs / FundPositionChannel / properties / account_channel / description
      Removed value: -"Broker channel identifier. Always emitted as `null` for privacy."
    • removedOutput schema / $defs / FundPositionChannel / properties / fund_info / description
      Removed value: -"Fund positions held in this channel."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `fund_positions`. Same channel-list shape as\n`StockPositionsResponse`, but with fund-specific position fields."
    • removedOutput schema / title
      Removed value: -"FundPositionsResponse"
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. First observedv0.1.12

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds a domain note about the fund identifier and ISIN, but that identifier is not present in the schema, and the description does not disclose return format, pagination, or other behavioral details. With annotations doing the heavy lifting, this is an adequate but not rich addition.

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 two short sentences and front-loads the core purpose. The second sentence is somewhat extraneous given the schema, but overall it is efficient and not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is read-only with no output schema and a single optional _jq parameter. The description gives almost no context for an agent to distinguish it from dozens of fund-related siblings, and it introduces a counter_id parameter that is absent from the schema, which may confuse invocation. It is not complete enough for confident selection and use.

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% for the only input parameter _jq, so the baseline is 3. The description instead discusses counter_id, which does not appear in the input schema, so it adds no meaning for the actual documented parameter. It does not compensate for any gap because there is no gap in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Get current fund positions.' However, it does not distinguish this tool from the many similar siblings such as fund_position, fund_position_overview, or stock_positions. It names the resource but leaves the agent to infer the difference between plural and singular or overview variants.

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?

There is no guidance on when to use this tool versus alternatives. The description only states what it does and adds a note about the fund identifier, but no context, prerequisites, or exclusions are provided.

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