Skip to main content
Glama
guangxiangdebizi

FinanceMCP

fund_manager_by_name

Query detailed information about a fund manager, including their managed funds, background, and career history, based on their name using the FinanceMCP server.

Instructions

根据基金经理姓名查询基金经理详细信息,包括管理的基金列表、个人背景、任职经历等

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ann_dateNo公告日期,格式为YYYYMMDD,如'20230101'。用于限制查询的公告日期
nameYes基金经理姓名,如'张凯'、'刘彦春'等

Implementation Reference

  • The main execution function for the 'fund_manager_by_name' tool. It fetches fund manager data from the TUSHARE API using the provided name and optional announcement date, processes and formats the response into a structured markdown output including personal info, managed funds, and statistics.
    export async function runFundManagerByName(args: { 
      name: string; 
      ann_date?: string; 
    }) {
      try {
        const TUSHARE_API_KEY = TUSHARE_CONFIG.API_TOKEN;
        const TUSHARE_API_URL = TUSHARE_CONFIG.API_URL;
    
        const data = await fetchFundManagerData(
          args.name,
          args.ann_date,
          TUSHARE_API_KEY,
          TUSHARE_API_URL
        );
    
        const formattedOutput = formatFundManagerData(data, args.name);
        
        return {
          content: [{ type: "text", text: formattedOutput }]
        };
    
      } catch (error) {
        return {
          content: [{ type: "text", text: `查询基金经理信息时发生错误: ${error instanceof Error ? error.message : String(error)}` }]
        };
      }
    } 
  • The tool definition object containing the name, description, and input schema for validation.
    export const fundManagerByName = {
      name: "fund_manager_by_name",
      description: "根据基金经理姓名查询基金经理详细信息,包括管理的基金列表、个人背景、任职经历等",
      inputSchema: {
        type: "object" as const,
        properties: {
          name: {
            type: "string",
            description: "基金经理姓名,如'张凯'、'刘彦春'等"
          },
          ann_date: {
            type: "string",
            description: "公告日期,格式为YYYYMMDD,如'20230101'。用于限制查询的公告日期"
          }
        },
        required: ["name"]
      }
    };
  • src/index.ts:168-172 (registration)
    Registration of the tool in the ListTools response handler, exposing it to MCP clients.
    {
      name: fundManagerByName.name,
      description: fundManagerByName.description,
      inputSchema: fundManagerByName.inputSchema
    },
  • src/index.ts:288-292 (registration)
    Dispatch case in the CallToolRequest handler that routes calls to the runFundManagerByName function.
    case "fund_manager_by_name": {
      const name = String(request.params.arguments?.name);
      const ann_date = request.params.arguments?.ann_date ? String(request.params.arguments.ann_date) : undefined;
      return await runFundManagerByName({ name, ann_date });
    }
  • Tool registration in the HTTP server's tool list for the /mcp tools/list endpoint.
    { name: fundManagerByName.name, description: fundManagerByName.description, inputSchema: (fundManagerByName as any).inputSchema },
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 describes a read-only query operation but doesn't disclose behavioral traits like rate limits, authentication needs, data freshness, error conditions, or response format. For a tool with no annotation coverage, this leaves critical operational context unspecified.

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, efficient sentence in Chinese that front-loads the core purpose. It wastes no words but could be slightly more structured (e.g., separating key details). Every part earns its place, though it lacks explicit formatting for clarity.

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, no output schema, and a query tool with two parameters, the description is incomplete. It doesn't cover return values, error handling, or operational constraints. While the purpose is clear, the lack of behavioral and output information makes it inadequate for confident tool invocation.

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%, so the schema fully documents both parameters (name and ann_date). The description adds no parameter-specific semantics beyond what's in the schema—it doesn't explain how parameters interact or provide usage examples. This meets the baseline for high schema coverage but doesn't add value.

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: querying fund manager details by name, with specific resources listed (managed funds, personal background, work experience). It distinguishes this from sibling tools like fund_data or stock_data by focusing on individual managers rather than fund or stock data. However, it doesn't explicitly differentiate from potential similar tools not present in the sibling list.

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. It doesn't mention prerequisites, constraints, or compare it to other tools for fund manager information. With sibling tools like fund_data potentially containing overlapping data, the lack of usage context is a significant gap.

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

Related 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/guangxiangdebizi/FinanceMCP'

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