Skip to main content
Glama

bim_product_detail

Fetch full details for a single BİM Aktüel product by its URL slug, including name, size, current TL price, large image URL, BİM id, slug, and url.

Instructions

Full detail of one Aktüel product. slug: the slug from a product URL (e.g. "aycicek-yagi-pet-sise-26-10" from /aktuel-urunler/aycicek-yagi-pet-sise-26-10/aktuel.aspx). Returns name, size, current price_try (TL), large image_url, BİM id, slug and url. Note: the detail page shows no brand — brand comes from bim_aktuel_products.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "bim_product_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the disclosure burden and does reasonably well: it enumerates the returned fields (name, size, price_try in TL, image_url, BİM id, slug, url) and flags an important limitation — the detail page carries no brand, which must come from bim_aktuel_products. It does not discuss failure behavior for an unknown slug or any caching/rate-limit traits.

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?

Front-loaded with the core purpose, then argument sourcing, then return contents, then the caveat. Every sentence adds usable information; the URL example is long but directly prevents a common calling error.

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 single-parameter lookup with an output schema present, the description covers the argument's origin, the return shape and the brand caveat, which is enough to call it correctly. The only gap is edge-case behavior when the slug does not resolve to a product.

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% and the only parameter is undocumented in the schema, so the description must compensate — and it does, defining slug as the segment from a product URL and giving a worked parsing example. There is no ambiguity left about the required argument's format.

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?

States a specific verb and resource: 'Full detail of one Aktüel product', and immediately scopes it to a single item identified by slug. It also names the sibling that supplies what this tool lacks (brand from bim_aktuel_products), so an agent can tell it apart from bim_aktuel_products without opening either schema.

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 concrete guidance on sourcing the required argument, showing exactly how to extract the slug from an URL path example. It also implicitly routes brand lookups elsewhere. What is missing is an explicit statement of when to prefer this over bim_aktuel_products (e.g. after listing to fetch price details).

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