Skip to main content
Glama

HarbiFırsat Deals (Turkey)

Fırsat ara / Search deals

search_deals
Read-only

Search active deals on HarbiFırsat (Turkish-aware: plurals, missing accents and small typos match). Optional filters: category slug, store slug, minimum discount %, maximum price (TRY).

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": {
      "query": "<query>"
    },
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-50)
queryYesSearch text, e.g. "kulaklık", "iphone 15", "lego"
storeNoStore slug from list_stores, e.g. "amazon"
categoryNoCategory slug from list_categories
max_priceNoMaximum price in TRY
min_discountNoMinimum discount percentage

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: matching is Turkish-aware and tolerant of plurals, missing accents and small typos, which materially affects how an agent should phrase queries. It does not discuss result ordering or empty-result behavior.

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?

Two short sentences, front-loaded with the verb and resource, followed by the filter list. Nothing is redundant or padded.

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 read-only filtered search with a fully documented schema and no output schema, the definition covers purpose, filters and matching behavior adequately. A brief note on what a returned deal contains or how results are ordered would close the remaining gap.

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?

Schema description coverage is 100%, so all six parameters are already documented and the description largely restates them (category slug, store slug, discount %, max price TRY). The one genuine addition is that the query parameter is matched fuzzily with Turkish normalization, which the schema does not say.

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 definition gives a specific verb and resource ("Search active deals on HarbiFırsat") plus the filter dimensions, so an agent knows exactly what operation this is. It stops short of differentiating itself from siblings such as get_hot_deals or get_store_deals, which cover overlapping territory.

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?

Usage is only implied: the presence of store/category filters hints that this is the keyword-search path while siblings handle browsing, but the description never says when to prefer it or when to use an alternative. No exclusions or prerequisites are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources