store

Compare Products

compare_products

Read-onlyIdempotent

Compare Bolot Studio products — Legacy Print vs Cinematic Print, or Bolot vs competitors (Displate, Canvas, Framed prints).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "comparison_type": "<comparison_type>"
    },
    "name": "compare_products"
  }
}

Input Schema

Name	Required	Description
`locale`	No	Locale code for localized URLs (e.g. 'en', 'pl', 'de')
`country`	No	ISO 3166-1 alpha-2 or alpha-3 country code for localized URLs (e.g. 'PL', 'DE', 'GB', 'DEU', 'GBR')
`product_handle`	No	Product handle for competitor comparison (defaults to 'the-legacy-print')
`comparison_type`	Yes	Type of comparison

Output Schema

Name	Required	Description	Default
`error`	No
`market`	No
`message`	No
`product`	No
`category`	No
`comparison`	No
`legacy_print`	No
`sustainability`	No
`vs_competitors`	No
`cinematic_print`	No
`differentiators`	No
`shared_features`	No
`_response_budget`	No
`quality_assurance`	No
`wall_art_launch_gate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 29, 2026
- removedOutput schema / properties / differentiators / items / properties / competitor_typical / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "boolean"
-  }
-]
```
- addedOutput schema / properties / differentiators / items / properties / competitor_typical / type
```
Added value: +[
+  "string",
+  "boolean"
+]
```
- removedOutput schema / properties / differentiators / items / properties / value / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "boolean"
-  }
-]
```
- addedOutput schema / properties / differentiators / items / properties / value / type
```
Added value: +[
+  "string",
+  "boolean"
+]
```

Changed1 schema field changedAug 14, 2026

addedOutput schema / properties / _response_budget

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "dropped": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "limit_bytes": {
+      "type": "number"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "dropped",
+    "limit_bytes",
+    "note"
+  ],
+  "type": "object"
+}

First observedJul 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — nothing about what the comparison returns, how locale/country affect the result, or that competitor comparisons are limited to the named brands.

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?

A single front-loaded sentence with no filler; the two supported comparison modes are the first thing read. Nothing is wasted.

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?

With an output schema, full schema coverage and read-only annotations, the description only needs to convey scope and it does. Minor gap: it never notes that the tool produces localized comparison page URLs keyed by locale/country, which is the main reason those two parameters exist.

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 genuinely adds meaning by naming the concrete subject of each enum value (Legacy vs Cinematic, and Bolot vs Displate/Canvas/Framed). That lets an agent pick comparison_type without reverse-engineering the enum tokens.

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 ('Compare') and resource ('Bolot Studio products') and enumerates the two comparison families, which map directly onto the legacy_vs_cinematic and vs_competitors enum values. It does not explicitly distinguish itself from siblings like search_products or get_product_recommendations, so it stops short of a 5.

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?

The description implies when to use it (when you need a Legacy vs Cinematic comparison or a Bolot vs competitor comparison), but it never states exclusions or points to an alternative tool. An agent must infer that SEO/comparison-page content is the intent rather than generic product lookup.

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

All store 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?