Skip to main content
Glama
Sign In

Teklif

by io.github.nietzische-app
OverviewDiscussionsAdmin

Compare offers

compare_offers
Read-only

Compares offers the user has explicitly asked to compare (by offer IDs from search_offers, or by category/city). If no IDs are given, returns up to 5 matching offers sorted by sort_by (default: the 5 lowest-priced). Returns offers with a card view. No paid or sponsored ranking. Operator-owned Aegis Scanner pricing.

Input Schema

NameRequiredDescriptionDefault
cityNoCity filter (example: İstanbul)
sort_byNoSort order: price (default), rating, or relevance. No paid placement.price
categoryNohepsi
offer_idsNoOffer IDs to compare (from search_offers). If omitted, up to 5 matching offers by category/city are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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 (örn. İstanbul)"New value: +"City filter (example: İstanbul)"
    • changedInput schema / properties / offer_ids / description
      Previous value: -"Karşılaştırılacak teklif id'leri (search_offers sonuçlarından). Boşsa kategori/şehir filtresine göre en uygunlar."New value: +"Offer IDs to compare (from search_offers). If omitted, up to 5 matching offers by category/city are returned."
    • removedInput schema / properties / platform
      Removed value: -{
-  "default": "chatgpt",
-  "enum": [
-    "chatgpt",
-    "claude",
-    "gemini"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / sort_by
      Added value: +{
+  "default": "price",
+  "description": "Sort order: price (default), rating, or relevance. No paid placement.",
+  "enum": [
+    "price",
+    "rating",
+    "relevance"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world, so the bar is low, yet the description adds real context: no paid or sponsored ranking, a hard result cap of 5, and a card-view return shape. The trailing "Operator-owned Aegis Scanner pricing" is opaque and doesn't clarify behavior.

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 that front-load the verb and the selection modes, with no filler. The final pricing/source note is abrupt and reads as a fragment rather than an integrated caveat.

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

Completeness5/5

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

No output schema exists, but the description covers the return shape (card view), the result cap, sorting, ranking neutrality, and all four parameters' roles. For a read-only comparison tool with zero required parameters this is sufficient to invoke correctly.

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 a solid 75%, and the description still adds behavioral meaning: offer_ids overrides category/city, and when omitted the tool returns up to 5 matching offers by default price order. The category enum values (addon, hepsi) remain undefined in both schema and description, and city takes no format guidance here.

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 ("Compares offers") plus the two selection modes: explicit offer IDs sourced from search_offers, or category/city filtering. This implicitly separates it from search_offers, though the boundary (search vs. compare) is never stated outright.

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?

Gives a clear trigger ("offers the user has explicitly asked to compare") and describes the fallback path when no IDs are supplied, including the cap of 5 and default sort. It stops short of an explicit exclusion telling the agent to call search_offers first when it has no IDs.

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