Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Fund Positions

fund_positions
Read-onlyIdempotent

Fetch current fund positions from your Longbridge account. Review holdings across US and HK markets to manage your portfolio.

Instructions

Get current fund positions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
  2. Addedv0.4.5
  3. Removedv0.4.0
  4. Addedv0.3.2
  5. Removedv0.3.1
  6. First observedv0.1.12

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety and behavior. The description adds no extra context beyond the name, but does not contradict annotations.

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?

A single, concise sentence with no wasted words. It is appropriately sized for a simple read-only tool.

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 presence of an output schema and comprehensive annotations, the description is minimally complete. It could be enriched with more detail about what fund positions include, but is sufficient for a straightforward retrieval tool.

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?

No parameters exist (0 params, 100% schema coverage). The description does not need to explain parameters. Baseline for zero params is 4.

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?

The description clearly states the tool retrieves current fund positions. It uses a specific verb ('Get') and resource ('current fund positions'), distinguishing it from sibling tools that handle different data types.

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 guidance on when to use this tool vs alternatives. The description does not mention exclusions, prerequisites, or context for its use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server