Skip to main content
Glama
Xxx00xxX33

FinanceMCP

by Xxx00xxX33

fund_manager_by_name

Find detailed information about fund managers by name, including their managed funds, career background, and professional experience. Input a manager's name to retrieve comprehensive financial profiles.

Instructions

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

Input Schema

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

Implementation Reference

  • The core handler function for the 'fund_manager_by_name' tool. It fetches data from Tushare API, processes it using helper functions, formats the output as structured Markdown, and returns it in MCP content format.
    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)}` }]
        };
      }
    } 
  • Tool schema definition including name, description, and input schema (parameters: name (required), ann_date (optional)).
    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:209-213 (registration)
    Registration of the tool in the MCP server's tools/list response.
    {
      name: fundManagerByName.name,
      description: fundManagerByName.description,
      inputSchema: fundManagerByName.inputSchema
    },
  • src/index.ts:329-333 (registration)
    Dispatch handler in the MCP server's tools/call request handler that invokes the tool's run 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 normalizeResult(await runFundManagerByName({ name, ann_date }));
    }
  • Dispatch handler in the HTTP server's tools/call endpoint that invokes the tool's run function.
    case 'fund_manager_by_name':
      return await runFundManagerByName({
        name: String(args?.name),
        ann_date: args?.ann_date ? String(args.ann_date) : undefined,
      });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a query operation ('查询'), implying it's likely read-only, but doesn't confirm this or describe other traits like error handling, rate limits, authentication needs, or response format. For a tool with no annotations, this leaves significant gaps in understanding its behavior beyond the basic purpose.

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, efficient sentence that front-loads the core purpose and lists key return details. Every part earns its place: it specifies the action, target, and information returned without redundancy or unnecessary elaboration. It's appropriately sized for a simple query tool.

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

Completeness3/5

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

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and return types but lacks behavioral context, usage guidelines, and output details. Without annotations or an output schema, the agent must infer behavior from the description alone, which is incomplete for safe and effective use. It meets the bare minimum but has clear gaps.

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?

The description doesn't add meaning beyond what the input schema provides. Schema description coverage is 100%, with clear documentation for both parameters ('name' and 'ann_date'), including examples and formats. The description mentions querying by name but doesn't elaborate on parameter usage, constraints, or interactions. With high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter semantics adequately.

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: '根据基金经理姓名查询基金经理详细信息' (query fund manager details based on name). It specifies the verb ('查询' - query) and resource ('基金经理详细信息' - fund manager details), and lists the types of information returned (managed fund list, personal background, work experience). However, it doesn't explicitly differentiate from sibling tools like 'fund_data' or 'stock_data', which might also involve fund-related queries.

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 any prerequisites, exclusions, or comparisons to sibling tools (e.g., 'fund_data' or others that might overlap with fund-related queries). Usage is implied only by the description's focus on fund manager details by name, but no explicit context or alternatives are provided.

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/Xxx00xxX33/FinanceMCP'

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