Skip to main content
Glama
kemalersin

FonParam MCP

by kemalersin

list_funds

List and filter investment funds in Turkey by type, risk level, management company, and other criteria to find suitable investment options.

Instructions

Yatırım fonlarını listeler ve filtreleme imkanı sunar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoSayfa numarası (varsayılan: 1)
limitNoSayfa başına kayıt sayısı (varsayılan: 20, maksimum: 100)
typeNoFon tipi
searchNoFon adı, kodu, şirket adı ile arama
codeNoFon kodu veya kodları (virgülle ayrılmış)
management_companyNoPortföy yönetim şirketi kodu
tefasNoTEFAS'ta işlem görme durumu
min_risk_valueNoMinimum risk seviyesi (1-7)
max_risk_valueNoMaksimum risk seviyesi (1-7)
sortNoSıralama alanı (code, title, yield_1y, vb.)
orderNoSıralama yönü

Implementation Reference

  • MCP tool handler for 'list_funds': validates input parameters using Zod schema and calls apiClient.listFunds to fetch the list of funds.
    case 'list_funds':
      const fundsParams = ListFundsSchema.parse(args);
      return await this.apiClient.listFunds(fundsParams);
  • Zod schema for validating input parameters of the list_funds tool.
    const ListFundsSchema = z.object({
      page: z.number().min(1).optional(),
      limit: z.number().min(1).max(100).optional(),
      type: z.nativeEnum(FundTypeEnum).optional(),
      search: z.string().optional(),
      code: z.string().optional(),
      management_company: z.string().optional(),
      tefas: z.boolean().optional(),
      min_risk_value: z.number().min(1).max(7).optional(),
      max_risk_value: z.number().min(1).max(7).optional(),
      sort: z.string().optional(),
      order: z.enum(['ASC', 'DESC']).optional()
    });
  • src/tools.ts:89-150 (registration)
    Tool registration in getTools(): defines name 'list_funds', description, and JSON inputSchema for MCP protocol.
    {
      name: 'list_funds',
      description: 'Yatırım fonlarını listeler ve filtreleme imkanı sunar',
      inputSchema: {
        type: 'object',
        properties: {
          page: {
            type: 'number',
            description: 'Sayfa numarası (varsayılan: 1)',
            minimum: 1
          },
          limit: {
            type: 'number',
            description: 'Sayfa başına kayıt sayısı (varsayılan: 20, maksimum: 100)',
            minimum: 1,
            maximum: 100
          },
          type: {
            type: 'string',
            description: 'Fon tipi',
            enum: Object.values(FundTypeEnum)
          },
          search: {
            type: 'string',
            description: 'Fon adı, kodu, şirket adı ile arama'
          },
          code: {
            type: 'string',
            description: 'Fon kodu veya kodları (virgülle ayrılmış)'
          },
          management_company: {
            type: 'string',
            description: 'Portföy yönetim şirketi kodu'
          },
          tefas: {
            type: 'boolean',
            description: 'TEFAS\'ta işlem görme durumu'
          },
          min_risk_value: {
            type: 'number',
            description: 'Minimum risk seviyesi (1-7)',
            minimum: 1,
            maximum: 7
          },
          max_risk_value: {
            type: 'number',
            description: 'Maksimum risk seviyesi (1-7)',
            minimum: 1,
            maximum: 7
          },
          sort: {
            type: 'string',
            description: 'Sıralama alanı (code, title, yield_1y, vb.)'
          },
          order: {
            type: 'string',
            description: 'Sıralama yönü',
            enum: ['ASC', 'DESC']
          }
        }
      }
    },
  • Core implementation in ApiClient: makes HTTP GET request to '/funds' endpoint with query parameters to retrieve paginated list of funds.
    async listFunds(params: ListFundsParams = {}): Promise<PaginatedResponse<Fund>> {
      const response: AxiosResponse<PaginatedResponse<Fund>> = await this.client.get('/funds', { params });
      return response.data;
    }
  • TypeScript interface defining the structure and types for ListFundsParams used in apiClient.listFunds.
    export interface ListFundsParams {
      page?: number;
      limit?: number;
      type?: FundTypeEnum;
      search?: string;
      code?: string;
      management_company?: string;
      tefas?: boolean;
      min_risk_value?: number;
      max_risk_value?: number;
      sort?: string;
      order?: 'ASC' | 'DESC';
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions listing and filtering capabilities, it doesn't describe important behavioral aspects: whether this is a read-only operation, what the response format looks like, whether it supports pagination (though parameters suggest it does), rate limits, authentication requirements, or any side effects. The description is minimal and leaves critical behavioral information unspecified.

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 extremely concise - a single Turkish sentence that directly states the tool's core functionality. There's no wasted language, repetition, or unnecessary elaboration. It's front-loaded with the primary purpose and efficiently communicates the essential capability. This is an excellent example of conciseness.

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?

For a tool with 11 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address the tool's behavioral characteristics, response format, error conditions, or how to interpret results. While the schema documents parameters well, the description fails to provide the contextual understanding needed to use this tool effectively, especially given the complexity implied by numerous filtering options.

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 schema description coverage is 100%, meaning all 11 parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond what's already in the schema - it doesn't explain parameter relationships, provide usage examples, or clarify how multiple filters interact. With complete schema documentation, the baseline score of 3 is appropriate since the description doesn't add value beyond the schema.

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: 'Yatırım fonlarını listeler ve filtreleme imkanı sunar' (Lists investment funds and provides filtering capability). It specifies the verb ('listeler' - lists) and resource ('yatırım fonları' - investment funds), and mentions filtering as an additional capability. However, it doesn't distinguish this tool from sibling tools like 'list_companies' or 'list_fund_types' that might also list different types of financial entities.

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. There are multiple sibling tools that could potentially overlap (like 'list_companies', 'list_fund_types', 'top_performing_funds'), but the description doesn't explain when this specific fund listing tool is appropriate versus those other listing tools. No usage context, prerequisites, or exclusions are mentioned.

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/kemalersin/fonparam-mcp'

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