Skip to main content
Glama
kemalersin

FonParam MCP

by kemalersin

company_details

Retrieve portfolio management company details and associated funds in Turkey using company codes to access investment data through FonParam API.

Instructions

Portföy yönetim şirketi detaylarını getirir

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesŞirket kodu
include_fundsNoŞirketin fonlarını da getir (varsayılan: true)

Implementation Reference

  • The MCP tool handler case in handleToolCall that validates input parameters using Zod schema and delegates to the API client method for fetching company details. Note: case label has a typo ('ompany_details') compared to the tool name.
    case 'ompany_details':
      const companyParams = CompanyDetailsSchema.parse(args);
      return await this.apiClient.getCompanyDetails(companyParams.code, companyParams.include_funds);
  • Zod schema for input validation of the company_details tool parameters: required code (string) and optional include_funds (boolean).
    const CompanyDetailsSchema = z.object({
      code: z.string(),
      include_funds: z.boolean().optional()
    });
  • src/tools.ts:305-322 (registration)
    Registration of the company_details tool in the getTools() method, including name, description, and input schema definition for MCP protocol.
    {
      name: 'company_details',
      description: 'Portföy yönetim şirketi detaylarını getirir',
      inputSchema: {
        type: 'object',
        properties: {
          code: {
            type: 'string',
            description: 'Şirket kodu'
          },
          include_funds: {
            type: 'boolean',
            description: 'Şirketin fonlarını da getir (varsayılan: true)'
          }
        },
        required: ['code']
      }
    },
  • API client helper method that performs the HTTP GET request to fetch company details from the backend API, including optional funds.
    async getCompanyDetails(code: string, includeFunds: boolean = true): Promise<CompanyDetails> {
      const params = { include_funds: includeFunds };
      const response: AxiosResponse<CompanyDetails> = await this.client.get(`/companies/${code}`, { params });
      return response.data;
    }
  • TypeScript interface defining the structure of the CompanyDetails response object, used for type safety in the tool implementation.
    export interface CompanyDetails {
      company: FundManagementCompany;
      stats?: CompanyStatistics;
    }
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. It states it retrieves details but doesn't specify what kind of details (e.g., financial data, contact info), whether it's a read-only operation, if there are rate limits, authentication needs, or error conditions. This leaves significant gaps for an agent to understand how to use it effectively.

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, concise sentence in Turkish that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool has no annotations and no output schema, the description is incomplete. It doesn't explain what details are returned, the format of the response, or any behavioral aspects like error handling. For a tool that likely returns structured company data, this lack of context makes it inadequate for an agent to use confidently.

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 adds no parameter information beyond what's already in the input schema, which has 100% coverage with clear descriptions for both parameters ('code' and 'include_funds'). Since the schema fully documents the parameters, the baseline score of 3 is appropriate as the description doesn't need to compensate but also doesn't add extra 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 verb ('getirir' - retrieves/fetches) and resource ('Portföy yönetim şirketi detaylarını' - portfolio management company details), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_companies' which might list companies without details, so it's not fully specific about what distinguishes this tool from alternatives.

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 when to choose this over 'list_companies' for details versus listing, or when to use it in relation to other tools like 'analyze_fund' or 'compare_funds'. There's no context about prerequisites or exclusions.

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