store

Start Configuration

start_configuration

Read-onlyIdempotent

Generate a direct URL to the Bolot Studio product configurator with pre-selected options. Optionally pre-select size and/or finish ('matte' or 'glossy'). Valid sizes are product-specific: 'the-legacy-print' accepts 'keepsake-3-pack' (three separate 13×9 cm panels with three separate metal desk stands), 'classic' (30×20), or 'statement' (42×30); 'the-cinematic-print' accepts 'intimate' (21×14), 'classic' (30×20), or 'statement' (42×30); 'the-address-sign' uses templates and ignores size/finish.

Input Schema

Name	Required	Description
`size`	No	Pre-select size. Valid set depends on the product: 'the-legacy-print' → 'keepsake-3-pack', 'classic', or 'statement'; 'the-cinematic-print' → 'intimate', 'classic', or 'statement'. The retired single token 'keepsake' is never accepted.
`finish`	No	Pre-select finish. Not applicable to address sign.
`locale`	No	Locale code (en, de, pl, etc.)
`country`	No	ISO 3166-1 alpha-2 or alpha-3 country code for market-visible product availability (e.g. 'DE', 'DEU')
`product_handle`	Yes	Product to configure

Output Schema

Name	Required	Description	Default
`note`	No
`error`	No
`locale`	No
`market`	No
`message`	No
`product`	No
`launch_gate`	No
`valid_sizes`	No
`instructions`	No
`pre_selected`	No
`requested_size`	No
`_response_budget`	No
`configurator_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 29, 2026
- removedOutput schema / properties / pre_selected / properties / finish / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / pre_selected / properties / finish / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / pre_selected / properties / size / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / pre_selected / properties / size / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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"
+}

Changed2 schema fields changedJul 25, 2026

changedInput schema / properties / size / description

Previous value: -"Pre-select size. Valid set depends on the product: 'the-legacy-print' → 'classic' or 'statement'; 'the-cinematic-print' → 'intimate', 'classic', or 'statement'. An unsupported size for the chosen product returns an invalid_size_for_product error. Not applicable to the address sign."New value: +"Pre-select size. Valid set depends on the product: 'the-legacy-print' → 'keepsake-3-pack', 'classic', or 'statement'; 'the-cinematic-print' → 'intimate', 'classic', or 'statement'. The retired single token 'keepsake' is never accepted."

changedInput schema / properties / size / enum

Previous value: -[
-  "classic",
-  "statement",
-  "intimate"
-]New value: +[
+  "keepsake-3-pack",
+  "classic",
+  "statement",
+  "intimate"
+]

First observedJul 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint and a closed-world profile, so the bar is lower; the description adds real context by disclosing that the output is a URL and that certain products silently ignore size/finish. It stops short of stating whether the URL is signed, expiring, or locale-dependent, which would have been useful.

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?

The purpose is front-loaded in the first sentence and the second sentence carries the option semantics without filler. The per-product size enumeration is dense and duplicates the enum mapping already present in the schema, costing some economy.

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 an output schema present, return format need not be explained, and the annotations cover the safety profile. The description supplies the product-specific size rules and the address-sign exception, which are the non-obvious things an agent needs to call this correctly.

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 would be 3, but the description adds genuine meaning beyond the schema: physical panel dimensions per size token, the three-panel composition of 'keepsake-3-pack', and the per-product valid size sets. Locale and country are left entirely to the schema, so it is not exhaustive.

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 artifact ('Generate a direct URL to the Bolot Studio product configurator') plus the scope of pre-selection. This is clearly distinguishable from siblings like search_products, compare_products, or get_product_recommendations, which do not return a configurator deep link.

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?

The description makes the use case evident (produce a pre-configured link with optional size/finish preselection) and includes a practical exclusion — 'the-address-sign' uses templates and ignores size/finish. It does not, however, explicitly name an alternative tool or state when not to call it.

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?