Skip to main content
Glama
Market Fiyatı MCP

Market Fiyatı MCP

by enesoglu

find_product

Read-onlyIdempotent

Look up a Turkish grocery product by provider ID or barcode to retrieve store offers with TRY prices, package quantities, and optional distance filtering by coordinates.

Instructions

Find by provider product ID or barcode. Set identity_type to id or barcode. A barcode match is distinct from fuzzy name similarity. Optional distance is in meters and requires latitude and longitude. Upstream errors are not empty results.

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": {
      "identity": "<identity>"
    },
    "name": "find_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
distanceNo
identityYes
latitudeNo
longitudeNo
identity_typeNoid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: 'Upstream errors are not empty results' warns the agent not to treat failures as zero matches, which matters a lot for an open-world lookup, and it states the coupling that distance requires latitude/longitude.

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 the identification method before the disambiguation and parameter constraints. The telegraphic style is efficient, though a couple of sentences ('Set identity_type to id or barcode') are terser than they need to be for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no output schema and no schema-level descriptions, the definition covers identity, barcode-vs-fuzzy and distance constraints well but omits what a successful result contains and what 'limit' controls. The error-vs-empty note helps, yet an agent still lacks enough to predict return shape.

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

Parameters3/5

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

With 0% schema description coverage the description must carry the full burden, and it partially does: it explains identity_type's two values, distance units (meters) and its lat/long dependency. However, the 'limit' parameter is never mentioned and 'identity' is only described indirectly via the opening sentence, leaving two of six parameters without added meaning.

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 opens with a specific verb and lookup key: 'Find by provider product ID or barcode,' which frames this as an exact-identity lookup rather than a discovery search. The sentence about barcode matching being 'distinct from fuzzy name similarity' carves out a clear boundary against sibling search tools without naming them.

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 gives concrete invocation guidance ('Set identity_type to id or barcode') and implicitly routes fuzzy/similar-name needs elsewhere by distinguishing barcode matches from fuzzy similarity. It stops short of explicitly naming the alternative tool or stating when-not-to-use conditions, so it falls short of a 5.

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