Skip to main content
Glama

HarbiFırsat Deals (Turkey)

Fırsat detayı / Deal details

get_deal
Read-only

Full details of one deal by its slug (the last part of a harbifirsat.net/deals/ URL).

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_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesDeal slug: the last part of a harbifirsat.net/deals/<slug> URL, or the slug field from other tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Deal slug: the last part of a harbifirsat.co/deals/<slug> URL, or the slug field from other tools"New value: +"Deal slug: the last part of a harbifirsat.net/deals/<slug> URL, or the slug field from other tools"
  2. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Deal slug: the last part of a harbifirsat.co/deals/<slug> URL, or the slug field from other tools"
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and scope profile is supplied structurally. The description adds the useful provenance hint that a slug is derived from a harbifirsat.net/deals/<slug> URL, but says nothing about what happens with an unknown slug, whether the result is cached/static, or what fields "full details" covers.

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 zero waste, front-loaded with the core action and resource, with the slug explanation placed inline as a parenthetical where it is needed.

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

Completeness3/5

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

For a one-parameter read tool with annotations covering safety, the definition is close to sufficient, but with no output schema the phrase "full details" leaves the shape of the response entirely unspecified. An agent cannot tell whether the response includes price, store, expiry, or images.

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?

There is a single parameter at 100% schema description coverage, and the schema text already explains the slug format including its origin from the URL. The description restates that same definition rather than adding new meaning such as accepted characters or slug-vs-id confusion, 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?

"Full details of one deal by its slug" names a specific verb (retrieve full details) and a specific resource (a single deal), and the slug-based lookup distinguishes it from the list/search siblings such as search_deals or get_store_deals. It stops short of explicitly naming an alternative, so it is clear but not fully differentiated.

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 reader infers this is the tool to call once a deal slug is known, presumably after search_deals or get_store_deals returns one. There is no explicit "use this when / don't use this when" statement and no alternative is named.

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