Skip to main content
Glama
akakce-mcp
by nsozturk

Akakçe product detail

akakce_product_detail

Retrieves full product details—name, brand, specs, average rating, price range, and all seller offers with shipping, delivery, and direct links—using a product code; an optional URL skips lookup.

Instructions

Bir ürünün tam detayını döndürür: ad, marka, teknik özellikler, ortalama puan, en düşük/en yüksek fiyat ve TÜM satıcıların listesi (fiyat, kargo, satıcı puanı, teslimat, satıcıya direkt gidiş linki). Sadece ürün code'u yeterli — URL otomatik çözülür. İstersen url (akakce_search'teki productUrl) vererek bir istek atlayabilirsin.

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

Input Schema

NameRequiredDescriptionDefault
urlNoÜrün sayfası URL'i (opsiyonel; verilirse code'dan çözmeye gerek kalmaz).
codeNoÜrün kodu (akakce_search/autocomplete sonucundan). Tek başına yeterli.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does disclose the return payload in detail plus the non-obvious behavior that the URL is resolved automatically from the code. It does not mention authentication, rate limits, or what happens when a code is invalid, which are the remaining behavioral gaps.

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 outcome (full detail plus all sellers) before the parameter tactics, and every clause carries information — the field enumeration, the auto-resolution, and the url shortcut each earn their place.

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 no output schema and no annotations, the description compensates well by enumerating the returned fields and the seller-list contents. Missing only edge-case behavior (errors, auth, whether the seller list is paginated or capped) for a fairly simple two-optional-param tool.

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?

Schema coverage is already 100%, so the baseline would be 3, but the description adds real meaning: `url` is an optional shortcut that costs one fewer request, and its value originates from akakce_search results. That is a usage relationship the schema text does not fully convey.

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 (döndürür) and resource (bir ürünün tam detayı) and enumerates exactly what comes back: name, brand, specs, rating, price range, and the full seller list. This lets an agent distinguish it from sibling tools like akakce_product_prices and akakce_quickview without opening their schemas.

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?

Explicitly says `code` alone is sufficient and that passing `url` (the productUrl from akakce_search) skips one request, giving a concrete provenance and a performance-based choice between the two params. It stops short of naming when to prefer this over akakce_quickview or akakce_product_prices, so it is strong but not exhaustive.

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