Skip to main content
Glama
Sign In

Teklif

by io.github.nietzische-app
OverviewDiscussionsAdmin

Search offers

search_offers
Read-only

Searches offers when the user asks for them, filtered by category (one_time, monthly, addon, or hepsi = all), optional city and optional maximum price in TRY. Returns matching offers sorted by sort_by (price | rating | relevance; default price, lowest first) and shows them as cards. No paid or sponsored ranking. Currently returns operator-owned Aegis Scanner plans from aegisscanner.com/landing#pricing.

Input Schema

NameRequiredDescriptionDefault
cityNoCity filter (case- and Turkish-diacritic-insensitive). Example: İstanbul, Ankara, İzmir, Bursa
budgetNoMaximum price in TRY. Example: 3000
sort_byNoSort order: price (lowest first, default), rating (highest first), or relevance (rating then price). No paid placement.price
categoryNoone_time | monthly | addon | hepsi (all)hepsi

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / budget / description
      Previous value: -"Maksimum fiyat (TRY). Örn. 3000"New value: +"Maximum price in TRY. Example: 3000"
    • changedInput schema / properties / category / description
      Previous value: -"arac_kiralama | e_ticaret | kasko | trafik_sigortasi | hepsi"New value: +"one_time | monthly | addon | hepsi (all)"
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "arac_kiralama",
-  "e_ticaret",
-  "kasko",
-  "trafik_sigortasi",
-  "hepsi"
-]New value: +[
+  "one_time",
+  "monthly",
+  "addon",
+  "hepsi"
+]
    • changedInput schema / properties / city / description
      Previous value: -"Şehir filtresi (büyük/küçük harf ve Türkçe karakter duyarsız). Örn. İstanbul, Ankara, İzmir, Bursa"New value: +"City filter (case- and Turkish-diacritic-insensitive). Example: İstanbul, Ankara, İzmir, Bursa"
    • removedInput schema / properties / platform
      Removed value: -{
-  "default": "chatgpt",
-  "description": "UTM için hedef asistan: chatgpt | claude | gemini",
-  "enum": [
-    "chatgpt",
-    "claude",
-    "gemini"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / sort_by
      Added value: +{
+  "default": "price",
+  "description": "Sort order: price (lowest first, default), rating (highest first), or relevance (rating then price). No paid placement.",
+  "enum": [
+    "price",
+    "rating",
+    "relevance"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description still adds real value: the default sort order, an explicit "No paid or sponsored ranking" guarantee, and a disclosure of what data currently backs results (operator-owned Aegis Scanner plans). It omits result-count limits and pagination, which would matter for a search tool.

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?

Three front-loaded sentences that move from purpose to filtering/sorting to data scope, with no filler. A few clauses duplicate the schema's enum and default documentation and could be cut.

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 search with full schema coverage and no output schema, the definition covers filters, default ordering, ranking neutrality, and current data provenance. Missing only result-size or empty-result behavior, which is minor at this complexity.

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 coverage is 100%, so the schema already documents city, budget, sort_by and category including enums and defaults. The description largely restates those ("hepsi = all", "default price, lowest first") and adds no format or edge-case semantics the schema lacks, so baseline 3 applies.

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 ("searches offers") plus the filter dimensions and the return shape (cards sorted by sort_by). It never names its siblings compare_offers or get_offer_link, so an agent must infer the boundary, which keeps it from a 5.

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?

"when the user asks for them" gives a minimal trigger condition, and the filter/sort vocabulary is spelled out, but there is no when-not guidance and no routing to compare_offers or get_offer_link. Usage is implied rather than prescribed.

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

All Teklif toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources