Skip to main content
Glama

HarbiFırsat Deals (Turkey)

Aktüel kataloglar / Grocery catalogs

get_latest_aktuel
Read-only

Latest weekly "aktüel" catalogs of Turkish grocery chains (BİM, A101, ŞOK, Migros, …). Without a brand: the newest catalog of every chain. With a brand slug: its last 5 catalogs. Each item links to the viewer.

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

Input Schema

NameRequiredDescriptionDefault
brandNoChain slug, e.g. "bim", "a101", "sok"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new behavior: result cardinality differs by mode (one per chain vs. last 5), and each item carries a viewer link. It stops short of describing freshness guarantees or whether stale catalogs are ever returned.

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?

Three short sentences with zero filler: what it is, then the two invocation modes, then a note on return shape. The most decision-relevant fact (no brand = all chains) is front-loaded.

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 single optional-parameter read tool with no output schema, the description is nearly sufficient — it signals the return shape ('each item links to the viewer') and the mode-dependent result size. It could say a bit more about what fields an item exposes beyond the link, but nothing essential for correct invocation is missing.

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 100% and the schema already gives example slugs, so the baseline is met. The description adds real meaning beyond the schema by explaining the two distinct result sets that depend on whether brand is supplied — information the schema does not convey.

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 resource and scope: 'Latest weekly aktüel catalogs of Turkish grocery chains', naming concrete chains. The verb/resource pairing is unambiguous and clearly distinct from deal-oriented siblings like get_hot_deals, though it never explicitly contrasts itself with them.

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 clear invocation context for both modes: omitting the brand returns the newest catalog per chain, supplying a slug returns that chain's last 5. It does not state when to prefer this over the sibling deal tools, so no explicit alternatives or exclusions are provided.

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