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

TableJSON 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

TableJSON 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

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description doesn't need to repeat safety traits. It adds valuable behavioral context beyond the schema, such as the address sign ignoring size/finish and specific physical dimensions for each size token.

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 description is a single, dense paragraph that front-loads the purpose and then provides product-specific rules. Every clause adds value, though it is slightly verbose due to the detailed size specifications. It is appropriately structured for the complexity.

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?

The description, combined with the full schema descriptions and annotations, thoroughly covers the tool's behavior. It specifies valid size/finish combinations, all product handles, and the address sign exception. Given the output schema exists, return values needn't be described.

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% with each property described, but the description adds meaningful detail beyond the schema, including physical dimensions (13×9 cm panels, 30×20, 42×30) and the address sign's template behavior. This enriches the parameter semantics.

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?

The description clearly states the tool generates a direct URL to the product configurator with pre-selected options, using a specific verb 'Generate' and a clear resource. It distinguishes itself from sibling tools that search, compare, or fetch product info.

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?

It provides detailed context on valid sizes per product and explicitly notes the address sign ignores size/finish, guiding correct usage. However, it does not explicitly name alternative tools or state when not to use this tool, so it lacks explicit exclusion criteria.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation3/5

Most tools hdistinct purposes, but search_products/search_products_task and check_photo_compatibility/check_photo_compatibility_task are direct-versus-task duplications of the same functionality. The descriptions note that one is task-based, so agents can tell them apart, but the overlap could still cause miselection.

Naming Consistency5/5

All tools use a consistent snake_case verb_phnoun pattern (get_, search_, check_, compare_, start_); task variants follow the same naming convention with a clear `_task` suffix. The convention is predictable and uniform.

Tool Count4/5

11 tools is within a reasonable range for a store assistant, and the scope covers discovery, comparison, recommendations, shipping, policies, and configuration. The two direct/task variant pairs add slight redundancy, making it feel a bit heavier than needed.

Completeness4/5

The tool surface covers core storefront workflows: product discovery/details, comparisons, recommendations, reviews, shipping, policies, photo compatibility, and configuration links. Snissing cart, checkout, or order-status tools feels acceptable if the server is scoped as a pre-purchase assistant, though those would be natural complements.

Resources

Need Help?