Skip to main content
Glama

KAP bildirimleri

finans_get_kap_disclosures

Retrieve public KAP disclosures for Borsa Istanbul companies, including material events and financial reports, using latest dates, a date range, and an optional stock ticker filter.

Instructions

Public disclosures from KAP (Kamuyu Aydınlatma Platformu) for Borsa Istanbul companies: material event disclosures (özel durum açıklaması), financial reports etc. Latest disclosures, or a date range optionally filtered by stock ticker (hisse kodu).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finans_get_kap_disclosures"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitisNoBitiş tarihi (YYYY-MM-DD). Boşsa bugün.
limitNoEn fazla kaç kayıt döndürülsün (1–200, varsayılan 20)
baslangicNoBaşlangıç tarihi (YYYY-MM-DD). Boşsa en son bildirimler.
hisseKoduNoHisse kodu, ör. THYAO. Verilirse tarih aralığı kullanılır (varsayılan son 7 gün).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the meaningful default (returns latest disclosures when no dates given) and that the ticker filter switches the range behavior. It says nothing about authentication, rate limits, result volume caps, pagination, or whether results are sorted newest-first, which are the traits an agent needs beyond the schema defaults.

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?

Two compact sentences, front-loaded with what the resource is and followed immediately by the two calling modes. The parenthetical Turkish expansion of KAP and özel durum açıklaması is slightly verbose but justified for disambiguation in a bilingual domain.

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?

For a 4-parameter, zero-required read tool with no output schema, the description covers the input modes but omits any indication of what a disclosure record contains (title, date, ticker, category, attachment) or how large a result set is returned. That gap matters precisely because no output schema exists to compensate.

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% and every parameter already carries a Turkish description with format and defaults, so the baseline is 3. The description reinforces the role of the ticker filter ('optionally filtered by stock ticker') and the date-range intent, but adds no format, precedence, or edge-case detail (e.g. what happens if both dates and ticker are omitted) 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 names the concrete resource (KAP public disclosures for Borsa Istanbul companies) and enumerates the content types it covers (material event disclosures, financial reports), so an agent knows exactly what data comes back. It does not, however, distinguish itself from the sibling finans_search_kap_companies, leaving the boundary between 'list disclosures' and 'search companies' implicit.

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?

It gives implied usage context — 'latest disclosures, or a date range optionally filtered by stock ticker' — which tells the agent two workable call patterns. There is no explicit when-to-use/when-not guidance and no pointer to an alternative tool for the company-lookup case, so selection against siblings is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.