Skip to main content
Glama
merkezekre2026

tefas-fund-comparator

list_funds

Retrieve a list of TEFAS mutual funds by category, with optional date range, code or name filters, and configurable result limit.

Instructions

List TEFAS funds by type and optional date range / filters.

Pulls general fund information (code, name, price, AUM, investors) from TEFAS via pytefas. By default returns a snapshot of the latest available day in the range (one row per fund).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows to return (1–500). Default 50.
end_dateNoRange end. Defaults to start_date when only start given.
fund_typeNoFund category. One of YAT (securities), EMK (pension), BYF (ETF), GYF (real estate), GSYF (venture capital). Aliases SEC/PEN/ETF/RE/VC also accepted. Default YAT.YAT
start_dateNoRange start as YYYY-MM-DD or DD.MM.YYYY. Defaults to today if omitted (with end_date).
latest_onlyNoIf true (default), keep only the most recent date in the range so each fund appears once.
code_containsNoCase-insensitive substring filter on fund code (e.g. "AA" matches AAK, AAL).
name_containsNoCase-insensitive substring filter on fund name (e.g. "ALTIN", "PARA PİYASASI").
output_formatNo``markdown`` (table) or ``json``.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/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 discloses the default behavior (latest_only true, one row per fund) and data source, but does not mention error handling, rate limits, or authorization needs. Adequate but not comprehensive.

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 highly concise, with two short paragraphs. The first sentence front-loads the main purpose, and every sentence contributes meaningful information. No redundancies.

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

Completeness4/5

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

Given the 8 well-documented parameters and the presence of an output schema, the description provides sufficient context for a listing tool. It explains the default single-date snapshot and data source. Minor gap: no mention of pagination or performance considerations for large date ranges.

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 baseline is 3. The description adds some context (e.g., summarizing output behavior) but does not significantly extend beyond what the schema already provides. Meets minimum expectations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists TEFAS funds by type and optional date range/filters, and specifies the data source and fields returned. It is easily distinguished from sibling tools like get_fund_details or analyze_performance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly provide when-to-use or when-not-to-use guidance, nor does it mention alternatives. The purpose is clear, but an agent lacks direct guidance on selecting this tool over siblings.

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/merkezekre2026/tefas-mcp'

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