Plendio price comparison

List brands

list_brands

Read-onlyIdempotent

Returns brands in Plendio's catalogue with the number of products each has and the url of its brand page on Plendio. With a query it finds brands whose name contains every word of it (accents ignored), brands that start with the query first; without one it lists the biggest brands. The product counts cover the whole catalogue, not one market. A page holds up to 96 brands.

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": "list_brands"
  }
}

Input Schema

Name	Required	Description
`page`	No	Result page of a search, 96 brands per page. Default 1.
`query`	No	Part of a brand name, e.g. "sony" or "bang olu". Empty lists the biggest brands.
`market`	No	Market for the brand page links: dk, se, de or no. Default: the market of the site you connected to.

Output Schema

Name	Required	Description
`page`	Yes
`notes`	No
`query`	No
`total`	Yes	How many brands match the query (0 without a query: the biggest brands are listed).
`brands`	Yes
`market`	Yes
`total_pages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, and the description goes further by disclosing matching semantics (all query words must appear, accents ignored, prefix matches ranked first), default ranking (biggest brands), page capacity (96), and that product counts span the whole catalogue rather than one market. That last point is non-obvious and prevents a real misinterpretation of results.

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 compact sentences, front-loaded with what is returned, then behavior, then a caveat, then a limit. Minor redundancy from repeating "on Plendio" and restating the page size in both the description and the schema, but nothing wasteful.

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?

An output schema exists, so return values need no explanation. The description covers the remaining decision-relevant facts an agent needs: matching rules, default ordering, count scope, and pagination size, which is complete for a read-only list tool with three optional parameters.

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; the description earns above that by explaining the matching and ranking rules behind `query` and the 96-per-page capacity behind `page`, which the schema only states as a count. It does not elaborate on `market` beyond what the schema already says about page links.

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 ("Returns brands in Plendio's catalogue") and enumerates the payload: product counts per brand plus the brand-page URL. This is clearly distinguishable from siblings like list_categories and search_products, which target different resources.

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 explicit conditional behavior: with a query it does word-wise, accent-insensitive matching with prefix prioritization; without one it lists the biggest brands. It does not explicitly name alternatives (e.g., when to prefer search_products over a brand query), so it stops short of full routing 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?