bim-mcp

bim_list_aktuel_dates

Lists BİM Aktüel and İndirim date periods with date keys, Turkish labels, and deal type so you can query products or price stats for a specific period.

Instructions

Aktüel and İndirim date periods on bim.com.tr, each with its date key (Bim_AktuelTarihKey), Turkish label (e.g. "03 Kasım Salı", "03-30 Kasım") and kind ("aktuel" or "indirim"). Use a key with bim_aktuel_products / bim_price_stats. No arguments.

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": "bim_list_aktuel_dates"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that the call takes no arguments and what each result contains, and read-only behavior is implied by 'list,' but it says nothing about data freshness, caching, or whether results are stable across calls — meaningful gaps for a scraped-listing tool.

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?

Four short sentences, front-loaded with what the tool returns before the workflow hint. The field enumeration slightly duplicates the output schema, but it is short and aids tool selection.

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?

With zero parameters and an output schema present, little description is strictly required, and the definition covers purpose, output shape, and the downstream key usage. Only freshness/refresh behavior is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. 'No arguments' is stated explicitly, removing any doubt about required input.

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 specific resource (Aktüel and İndirim date periods on bim.com.tr) and enumerates the returned fields (date key, Turkish label, kind), so an agent knows exactly what the tool yields. It lacks an explicit verb, but the listing nature is unambiguous from the name and content.

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

Usage Guidelines4/5

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

It states the downstream workflow explicitly: 'Use a key with bim_aktuel_products / bim_price_stats,' which tells the agent this is a prerequisite enumeration step. It does not say when NOT to use it or how often the dates change, but the primary usage path is clear.

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

Deploy Server