Bestshopping Cashback — IT, DE, FR

get_merchant

Read-onlyIdempotent

Read current public merchant information, cashback conditions and browser tracking rules. Exact cashback rates must be checked on the returned Bestshopping page; this tool does not provide a personalized quote or access an account.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`market`	Yes	Bestshopping ACCOUNT market: it (Italy), de (Germany), fr (France). Ask the user if missing or ambiguous; never infer it from language or reuse IDs across markets.
`merchant_id`	Yes	Merchant ID returned by search_merchants. Never guess or reuse IDs from another market.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`merchant`	Yes
`checked_at`	Yes
`conditions`	Yes
`description`	Yes
`rate_notice`	Yes
`cashback_rate`	Yes
`tracking_rules`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 21, 2026

removedInput schema / properties / market / default
```
Removed value: -"it"
```

changedInput schema / properties / market / enum

Previous value: -[
-  "it"
-]New value: +[
+  "it",
+  "de",
+  "fr"
+]

changedInput schema / required

Previous value: -[
-  "merchant_id"
-]New value: +[
+  "merchant_id",
+  "market"
+]

changedOutput schema / properties / merchant / properties / market / enum

Previous value: -[
-  "it"
-]New value: +[
+  "it",
+  "de",
+  "fr"
+]

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / market / description

Previous value: -"Bestshopping market. Only Italy is enabled."New value: +"Bestshopping ACCOUNT market: it (Italy), de (Germany), fr (France). Ask the user if missing or ambiguous; never infer it from language or reuse IDs across markets."

removedOutput schema / properties / merchant / properties / market / const
```
Removed value: -"it"
```
addedOutput schema / properties / merchant / properties / market / enum
```
Added value: +[
+  "it"
+]
```

First observedOct 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context: the data is public, not account-specific, and exact cashback rates must be checked on the returned Bestshopping page. It does not cover auth or rate limits, but it meaningfully supplements the annotations.

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?

The description is two sentences: the first front-loads the tool's purpose, and the second adds a necessary limitation. Every sentence carries useful information with no waste.

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?

Given rich annotations, a full output schema, and 100% parameter coverage, the description is complete enough for an agent to understand the tool's scope and limitations. It clearly says what information is returned and what it does not provide.

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 required parameters are fully documented in the schema. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 verb and resource: 'Read current public merchant information, cashback conditions and browser tracking rules.' The scope is clear, but the description does not explicitly differentiate it from sibling tools such as search_merchants or prepare_cashback_link.

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?

It provides a caveat about what the tool does not do ('does not provide a personalized quote or access an account'), but it does not explicitly say when to use this tool versus search_merchants or prepare_cashback_link. The usage is implied by the merchant_id and market requirements rather than stated in the description.

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

All Bestshopping Cashback — IT, DE, FR tools Inspect

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

Need Help?