Skip to main content
Glama
ariesanhthu

VNStock MCP Server

by ariesanhthu

get_fund_nav_report

Retrieve net asset value (NAV) reports for mutual funds from the Vietnam stock market, supporting JSON or DataFrame output formats.

Instructions

Get nav report of a fund from stock market
Args:
    symbol: str (symbol of the fund to get nav report)
    output_format: Literal['json', 'dataframe'] = 'json'
Returns:
    pd.DataFrame

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
output_formatNojson

Implementation Reference

  • The main handler function for the 'get_fund_nav_report' tool. It is decorated with @server.tool(), which registers it as an MCP tool. The function fetches the NAV report for a given fund symbol using the FMarketFund class from vnstock and returns it in JSON or DataFrame format.
    @server.tool()
    def get_fund_nav_report(
        symbol: str, output_format: Literal["json", "dataframe"] = "json"
    ):
        """
        Get nav report of a fund from stock market
        Args:
            symbol: str (symbol of the fund to get nav report)
            output_format: Literal['json', 'dataframe'] = 'json'
        Returns:
            pd.DataFrame
        """
        fund = FMarketFund()
        df = fund.details.nav_report(symbol=symbol)
        if output_format == "json":
            return df.to_json(orient="records", force_ascii=False)
        else:
            return df
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the return type ('pd.DataFrame') which is helpful, but doesn't disclose important behavioral traits: whether this is a read-only operation, if it requires authentication, rate limits, error conditions, or what happens with invalid symbols. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 appropriately sized and well-structured with clear sections (Args, Returns). The purpose statement is front-loaded, and each sentence serves a purpose. However, the formatting with quotes and line breaks could be cleaner, and the 'Returns: pd.DataFrame' contradicts the output_format parameter's default of 'json', creating some confusion.

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?

Given no annotations, 0% schema description coverage, and no output schema, the description is incomplete. While it mentions the return type, it doesn't explain the NAV report structure, data fields, or what 'nav report' actually contains. For a financial data tool with many sibling alternatives, more context about the specific data returned would be necessary for an agent to use it effectively.

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 0%, so the description must compensate. It provides basic type information for parameters ('symbol: str', 'output_format: Literal['json', 'dataframe']') and a default value, which adds meaning beyond the bare schema. However, it doesn't explain what 'symbol' represents (ticker symbol? fund identifier?), acceptable formats, or constraints. The description adds some value but doesn't fully compensate for the 0% schema coverage.

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 nav report of a fund from stock market' - a specific verb ('Get') and resource ('nav report of a fund'), with context about the data source ('from stock market'). It distinguishes from siblings like 'get_fund_asset_holding' or 'get_fund_top_holding' by focusing on NAV reports specifically. However, it doesn't explicitly differentiate from all siblings, keeping it at 4 rather than 5.

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. With many sibling tools available (like 'get_fund_asset_holding', 'get_fund_industry_holding', 'list_all_funds'), there's no indication of when this specific NAV report tool is appropriate versus other fund-related tools. The description only states what it does, not when to choose it.

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/ariesanhthu/mcp-server-vietnam-stock-trading'

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