Skip to main content
Glama

bim_aktuel_products

Fetch priced BİM Aktüel products for a chosen week, with optional Turkish keyword filtering, sorting by price or name, and limits. Returns brand, size, price in TL, image and product URL.

Instructions

Priced Aktüel products for one week. date_key: a key from bim_list_aktuel_dates; omit for the current week. query: optional Turkish substring filter over brand + name + size (e.g. "yağ", "pirinç", "süt"). sort: "price_asc", "price_desc" or "name" (default: page order). limit 1..100 (default 50). Returns brand, name, size, price_try (TL), image_url, product url, slug and BİM id per product.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
queryNo
date_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the read-only listing behavior, default paging (limit 50, max 100), default 'page order' sort, and the exact data returned. It omits error behavior for an invalid date_key and any rate/auth constraints, which keeps it below a 5.

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?

Front-loaded purpose followed by a compact per-parameter walkthrough; nearly every clause earns its place. The trailing return-field list partially duplicates the output schema, which is the one source of redundancy.

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?

For a four-param, zero-annotation listing tool this is close to complete — parameter sourcing, filtering, sorting, and paging are all covered, and the output schema covers return values. Only failure modes and a sibling contrast are missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry all meaning, and it does: date_key's provenance and default, query's scope (brand + name + size) with Turkish examples, the three sort values plus the default, and the limit range 1..100. Every parameter is disambiguated beyond the bare schema types.

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 scope: priced Aktüel products scoped to a single week, with the return fields enumerated. It doesn't explicitly contrast with siblings like bim_product_detail, but the list-versus-detail shape is inferable from 'per product' plus the paging params.

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?

Gives an explicit prerequisite chain: take date_key from bim_list_aktuel_dates, or omit it to get the current week. No explicit when-not guidance against sibling product tools, but the operational usage is clear.

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