Skip to main content
Glama

BIST endeks bileşenleri

finans_get_bist_index

Retrieve Borsa Istanbul index constituents for a given index code or identify which indices a stock ticker belongs to, supporting market analysis and portfolio research.

Instructions

Borsa Istanbul index constituents (endeks bileşenleri: BIST 30/XU030, BIST 100/XU100, XBANK…) or, given a ticker, which indices that stock belongs to.

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_bist_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
hisseNoHisse kodu verilirse dahil olduğu endeksler, ör. "ASELS"
endeksNoEndeks kodu, ör. "XU030", "XU100", "XBANK"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the tool's dual-direction behavior, which is real value, but omits that this is a read-only reference lookup, what the result shape looks like, and the zero-argument behavior implied by 0 required parameters. Adequate but not rich.

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?

A single sentence that front-loads the primary function and then qualifies it with the inverse lookup. Nothing is wasted and the bilingual parenthetical aids disambiguation without bloat.

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?

This is a simple two-optional-parameter lookup with no output schema, so the description need not explain return values. However, for a tool with zero required parameters, the silent no-argument case and whether the two filters compose are genuine gaps an agent would need to guess at.

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 coverage is 100%, so both parameters are already documented in the schema, and the description only restates their effect at a high level. It does clarify the functional outcome of each parameter (constituents vs. membership), which is mildly additive. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States a specific resource and both directions of the lookup: 'Borsa Istanbul index constituents' and, given a ticker, 'which indices that stock belongs to'. This is clearly distinguishable from sibling tools such as finans_get_stock_history or finans_get_exchange_rates. It stops short of naming a sibling it must not be confused with, so it is a 4 rather than a 5.

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 implies two usage modes (pass an index to get constituents, pass a ticker to get memberships) but never says so explicitly as when-to-use guidance. Crucially, both parameters are optional and the description never explains what happens when neither is supplied, nor whether both can be combined in one call. Usage is inferable but not stated.

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