Plendio price comparison

Search products

search_products

Read-onlyIdempotent

Search Plendio's product catalogue: free text in Danish, Swedish, German, Norwegian or English ("laptop 32 GB RAM under 12000", "Sony WH-1000XM5", "running shoes women") plus optional filters. Spec words in the query (RAM, storage, screen size, price limits, in stock) are understood the way the Plendio website understands them. Each result has the cheapest current price, the number of shops selling it and the url of its Plendio page. Results are limited to shops that ship to the market unless include_other_markets is true. 24 results per page.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Result page, 24 products per page. Default 1.
`sort`	No	relevance (default), price_asc or price_desc.
`query`	Yes	What to look for, in any of the market languages or English: a product name, a type, or a description with specs and limits ("laptop 32 GB RAM under 12000"). Required unless category is given.
`shops`	No	Only offers from these shops, by domain, e.g. ["elgiganten.dk"].
`brands`	No	Only these brands (up to 25), e.g. ["Sony","Bose"].
`market`	No	Market to search: dk, se, de or no. Default: the market of the site you connected to (plendio.dk is dk).
`category`	No	Category slug to narrow the search to, e.g. computere.
`in_stock`	No	Only products that at least one shop has in stock.
`max_price`	No	Highest price, in the market's currency (major units).
`min_price`	No	Lowest price, in the market's currency (major units, e.g. 500 means 500 kr.).
`include_other_markets`	No	Also include products no shop ships to the market. Default false: only products the market's shoppers can have delivered.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes
`notes`	No
`query`	Yes
`total`	Yes	Number of matching products.
`market`	Yes
`applied`	No	Filters the search applied, including ones it read from the query text.
`currency`	Yes	Currency of the market.
`products`	Yes
`page_size`	Yes
`search_url`	Yes	The same search on the Plendio website.
`total_exact`	Yes	False when total is a lower bound ("at least").
`total_pages`	Yes
`did_you_mean`	No	Set when the results answer a corrected spelling of the query.
`understood_as`	No	Set when the query was a sentence: the product searches it was read as, which the results answer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

addedOutput schema / properties / understood_as

Added value: +{
+  "description": "Set when the query was a sentence: the product searches it was read as, which the results answer.",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

First observedSep 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds real operational context beyond them: results are restricted to shops that ship to the market unless include_other_markets is true, and pagination is fixed at 24. It still doesn't hint at ranking behavior beyond the sort enum, but the added constraints are substantive.

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?

Four sentences, front-loaded with purpose before the market/pagination caveats. Every sentence carries information, though the result-shape sentence slightly overlaps with what the output schema provides.

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?

With 11 parameters all documented, an output schema covering return values, and annotations covering safety, the description fills the remaining gaps (market-shipping restriction, page size, query interpretation) without redundancy.

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 meaning the schema does not: spec words in the query (RAM, storage, price limits, in stock) are interpreted the way the Plendio site interprets them, and the multi-language query framing clarifies the query field's intent.

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 ('Search Plendio's product catalogue') and immediately scopes it as free-text across five languages with optional filters. An agent can distinguish this from get_product (single retrieval), compare_prices, and list_categories without opening any 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?

Gives clear context for when the tool applies — free-text queries with embedded specs plus optional filters — and the example queries illustrate the intended input style. It does not explicitly name when to prefer a sibling (e.g. get_product for a known product), so it stops short of full when/when-not guidance.

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

All Plendio price comparison 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?