Skip to main content
Glama

HarbiFırsat Deals (Turkey)

Mağaza fırsatları / Store deals

get_store_deals
Read-only

Newest active deals of one store, by store slug (see list_stores).

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": {
      "slug": "<slug>"
    },
    "name": "get_store_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesStore slug from list_stores, e.g. "amazon", "trendyol"
limitNoMax results (1-50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Store slug from list_stores, e.g. \"amazon\", \"trendyol\""
  2. 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=true and openWorldHint=false, so safety is covered; the description still adds real behavioral detail by disclosing that results are restricted to active deals and ordered newest-first. It does not cover pagination or what happens when a store has no active deals, but the filter and ordering semantics are the substantive contribution here.

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?

A single sentence that front-loads the core semantics (newest active deals, one store) with the slug provenance tucked into a short parenthetical. 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 two-parameter, read-only lookup with full schema coverage and no output schema, the description supplies what an agent needs: the scoping, the ordering/filter semantics, and how to acquire the required slug. Only the absence of any note on empty results or result-shape expectations keeps it from being fully complete.

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 both slug and limit are already documented with format hints and bounds in the schema. The description only reinforces that slug identifies a single store and points at list_stores as the source, which is consistent but adds little beyond the structured fields; 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?

"Newest active deals of one store, by store slug" names the resource (deals), the scope (one store), and the filter/order (newest, active), which separates it from a global hot-deals or search tool. It stops short of naming which sibling performs the broader search, so differentiation is implied rather than explicit.

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?

The parenthetical "(see list_stores)" gives a concrete prerequisite for obtaining the required slug, which is genuine usage guidance. However, there is no statement of when to prefer this over get_hot_deals or search_deals, nor any exclusion case, so the agent must infer the boundary.

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