Skip to main content
Glama
Market Fiyatı MCP

Market Fiyatı MCP

by enesoglu

search_products

Read-onlyIdempotent

Find Turkish grocery products by keyword and compare up to 20 store offers per item, with TRY prices, provenance flags, and optional location filtering.

Instructions

Search Turkish grocery products. Optional location requires all three fields; distance is in meters (100–50000). Returns up to 25 products and 20 cheapest returned offers per product, TRY prices, provenance and truncation flags. Results are provider snapshots, not guaranteed checkout prices. Do not invent a location.

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": {
      "keywords": "<keywords>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
distanceNo
keywordsYes
latitudeNo
longitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing result caps (up to 25 products, 20 cheapest offers per product), currency (TRY), inclusion of provenance and truncation flags, and the important caveat that results are provider snapshots rather than guaranteed checkout prices. That is exactly the kind of staleness/trust context an agent needs and the annotations cannot express.

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?

Dense, front-loaded and free of filler; the constraint about inventing a location is placed at the end as an emphatic warning. It packs a lot into four sentences without becoming noisy, though the return-format details could be ordered slightly more crisply.

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?

No output schema exists, so the description must describe returns, and it does: caps, currency, provenance and truncation flags. Missing pieces are the meaning of 'limit', behavior when no location is supplied, and empty-result handling, but the core call semantics are covered.

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?

With 0% schema description coverage, the description carries the parameter burden and does well: it defines distance units and bounds (meters, 100–50000) and the all-three-or-none coupling of latitude/longitude/distance. It does not explain the 'limit' parameter or reconcile it with the stated 25-product cap, which is a real gap.

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 verb and resource ('Search Turkish grocery products'), which is immediately actionable. It does not explicitly differentiate itself from siblings like find_product or find_similar_products, so sibling routing is left to the caller.

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?

Gives a concrete usage rule for the location fields ('Optional location requires all three fields' and 'Do not invent a location'), which is genuinely helpful. However it never says when to prefer this over find_product or find_similar_products, so guidance toward alternatives is absent.

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

Deploy Server

Other Tools