Skip to main content
Glama

HarbiFırsat Deals (Turkey)

Sıcak fırsatlar / Hot deals

get_hot_deals
Read-only

Today's hottest deals on HarbiFırsat, ranked by community votes with time decay (like the site's front page).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hot_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-50)

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=true and openWorldHint=false, yet the description adds genuinely new behavioral context: results are ordered by community votes with time decay, and the time scope is limited to today. Knowing the ordering scheme matters for interpreting output order and for deciding whether to re-fetch. It does not discuss pagination beyond the limit cap, which keeps it from a 5.

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 with the resource and recency scope front-loaded, followed by the ranking mechanism and a compact parenthetical analogy. No filler, no repetition of the schema or annotations.

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 one-optional-parameter, read-only list tool with no output schema, the definition covers what it returns, how it is ordered, and the time window — enough to call it correctly. Minor gaps remain about the shape of a deal record and whether results are limited to 'today' by definition rather than by a parameter.

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 one optional parameter at 100% schema description coverage, the schema already documents limit (1-50, default 10) fully. The description adds no syntax or behavioral nuance about limit and does not mention that the result window is fixed to 'today' with no date parameter — schema carries the burden, so baseline 3.

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 names a specific verb+resource (get today's hottest deals) and pins down the ranking logic — community votes with time decay — plus the 'front page' analogy so the agent knows this is a curated popularity feed. It stops short of naming which sibling (search_deals, get_latest_aktuel, get_store_deals) to use instead, 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?

Usage is implied by 'Today's hottest deals ... like the site's front page', which signals a browse/discovery use case rather than a targeted lookup. There is no explicit statement of when to prefer this over search_deals or get_latest_aktuel, and no exclusions or prerequisites.

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