Skip to main content
Glama
Sign In

Fordeal

by ai.fordeal
OverviewDiscussionsAdmin

Check a shop's product feed and preview its offers

check_shop_feed
Read-onlyIdempotent

Before or instead of registering: reads one product feed and answers whether Fordeal can use it. Give the feed's public address in feed_url (read through the SSRF guard: public hosts only, FordealBot, robots.txt respected, 20 s cap) or the file itself in feed_content (XML or CSV text, at most 8 MB) or feed_base64 (a gzip-packed file; ZIP is refused), plus the shop's delivery country and, with a file, its domain. The answer: health ok | warn | fail, counts (items, skipped, with EAN, price, picture, availability, shipping, category), coded issues (no_items, items_skipped, feed_unreadable, price_zero, currency_mismatch, url_not_shop_host, duplicate_item_id, encoding_suspect, price_outlier, missing_ean, availability_unknown, shipping_missing, image_missing, category_missing, stale_feed) with the first affected items by the shop's own id and name, blocking = the error codes to fix first, validation = the required-field check (title, price, URL, EAN) in Czech sentences for Heureka, Zboží, Google and CSV feeds, and preview.shown = the first items as the comparison would show them (goods price, shipping to the country from the feed, total, stock, picture, what each lacks). Nothing is stored and nothing is mailed. A feed that cannot be read answers health fail with read_error {code, message, fix}. Next: register_shop with the same feed. Public; ten checks a minute per caller.

Input Schema

NameRequiredDescriptionDefault
domainNoThe shop's host, e.g. www.obchod.cz; required with a file, the feed's host by default.
formatNoThe feed format when known; detected from the content otherwise.
countryYesThe shop's delivery country (ISO code from GET /api/v1/deals/countries): its currency and the shipping the total uses.
feed_urlNoThe feed's public address (Heureka, Zboží, Google Merchant, Ceneo, Idealo, Árukereső XML or CSV). Either this or a file.
filenameNoThe file's name, echoed back.
feed_base64NoThe feed file's bytes as base64, for a gzip-packed file (.xml.gz). ZIP is refused.
feed_contentNoThe feed file as text (XML or CSV), at most 8 MB. Over MCP the whole request is limited to 2 MB; send bigger files to POST /api/v1/shops/feed-check.
preview_itemsNoHow many items the preview shows (default 6, at most 24).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "heureka",
-  "zbozi",
-  "google",
-  "csv",
-  "ceneo",
-  "idealo",
-  "arukereso",
-  "glami"
-]New value: +[
+  "heureka",
+  "zbozi",
+  "google",
+  "csv",
+  "ceneo",
+  "idealo",
+  "arukereso",
+  "glami",
+  "awin"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial extra context: the SSRF guard, public-hosts-only rule, FordealBot agent, robots.txt respect, 20 s cap, 8 MB / 2 MB size ceilings, ZIP refusal, the 'nothing is stored and nothing is mailed' guarantee, and a 10-per-minute rate limit.

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?

Purpose and the primary input choice are front-loaded, and every clause carries information. It is however a single dense paragraph that mixes input rules, output shape and rate limits together, which makes it harder to scan than it needs to be.

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?

There is no output schema, so the description carries the return contract itself, and it does: health states, item counts, the full coded-issue list, blocking codes, the per-format validation sentences, preview.shown fields and the read_error case. Little an agent needs to call or interpret it 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%, so the baseline is 3, but the description adds real meaning: the three feed inputs are alternatives ('or the file itself'), domain is required alongside a file and defaults to the feed's host, and country determines the currency and shipping used in the total.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('reads one product feed and answers whether Fordeal can use it') and frames it against the registration flow, so an agent can separate it from register_shop and get_shop_feed_diagnostics without opening a schema.

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?

'Before or instead of registering' gives clear timing, and 'Next: register_shop with the same feed' names the follow-on tool. It stops short of saying when to prefer get_shop_feed_diagnostics or list_my_shops instead, so no explicit exclusion is offered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fordeal 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