Design & price modular raised garden beds and walls: exact bill of materials, EUR price + checkout.
Scored across 5 tools
The tools are mostly distinct: catalog_bricks, design_rules, and templates_list have clear, separate informational purposes. However, bom_to_cart and pricing_quote both compute BOM and price, differing only in that one creates a cart and returns a checkout URL while the other just returns a quote, which could cause an agent to select the wrong one without careful reading.
All tools follow a consistent snake_case convention with the 'studio_' prefix, and the second part is descriptive (e.g., 'bom_to_cart', 'catalog_bricks', 'design_rules'). While some are noun-heavy (catalog_bricks, design_rules) rather than strict verb_noun, the pattern is predictable and readable, with only minor deviations from a pure verb-first naming style.
Five tools is well-scoped for a design-and-purchase utility. Each tool covers a distinct stage: discovering templates, catalog items, rules, pricing, and finally creating a cart. No tools feel redundant or superficial; the count is appropriate for the server's purpose.
The tool surface covers the core workflow: listing shapes, components, rules, computing pricing, and building a cart. There is no tool to validate a design against the rules (only references to view rules), and no update/delete operations are relevant for this domain. Minor gaps exist, but they are not likely to cause agent failures in the primary use case.
Build a ready-to-pay Shopify cart for a GridGarden Brick Premium raised bed (rectangle / L / U) or wall from millimetre dimensions, and return the checkout URL. Computes the exact bill of materials, maps it to the live Brick Premium product variants, and creates an ANONYMOUS cart — no account, login, or payment occurs; the user reviews and pays on gridgarden.eu. Returns checkout_url, total EUR, and the line items.
| Name | Required | Description | Default |
|---|---|---|---|
| shape | Yes | Design type and the dimension fields it needs (all in mm, auto-snapped to the 60mm build grid): rectangle → length + width; lshape → length1 + width1 + length2 + width2; ushape → topLength + topWidth + arm1Length + arm1Width + arm2Length + arm2Width; wall → wallLength. Layers: raised beds 2–13, walls 1–25. Call studio_templates_list for ready example dimensions. | |
| width | No | Rectangle: outer width in mm. | |
| layers | Yes | Number of brick layers. Raised beds 2-13, walls 1-25 (1 = a single 60mm top-cap course). Each layer ≈120mm tall (top layer +60mm). | |
| length | No | Rectangle: outer length in mm. | |
| width1 | No | L-shape: first leg width in mm. | |
| width2 | No | L-shape: second leg width in mm. | |
| country | No | Delivery market as an ISO-3166-1 alpha-2 code (e.g. "DE", "AT", "SK"). Prices differ by market: SK and CZ are base, every other EU market adds €1 per structural piece. Ask which country the order ships to; omit only if unknown — that returns base (SK/CZ) prices. | |
| length1 | No | L-shape: first leg length in mm. | |
| length2 | No | L-shape: second leg length in mm. | |
| topWidth | No | U-shape: back (top) width in mm. | |
| arm1Width | No | U-shape: arm 1 width in mm. | |
| arm2Width | No | U-shape: arm 2 width in mm. | |
| topLength | No | U-shape: back (top) length in mm. | |
| arm1Length | No | U-shape: arm 1 length in mm. | |
| arm2Length | No | U-shape: arm 2 length in mm. | |
| utm_source | No | Attribution source recorded on the Shopify cart (UTM). Defaults to "mcp". | |
| wallLength | No | Wall: single straight segment length in mm. |
| Name | Required | Description |
|---|---|---|
| cart_id | Yes | |
| snapped | No | |
| summary | Yes | |
| currency | Yes | |
| total_eur | Yes | |
| editor_url | Yes | |
| line_items | Yes | |
| price_basis | Yes | |
| checkout_url | Yes | |
| total_quantity | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that it creates an anonymous cart without auth or payment, and returns a checkout URL, complementing destructiveHint=true. It adds context about bill-of-materials computation and variant mapping beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each adding unique information: purpose/scope, internal process and safety, and return values. No redundant words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex 17-parameter tool with rich schema and output schema, the description covers the end-to-end behavior, side effects, and return values sufficiently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with detailed descriptions. The description adds no additional parameter meaning beyond what the schema already provides, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: builds a ready-to-pay Shopify cart and returns the checkout URL. It distinguishes from sibling tools by focusing on cart creation rather than catalog, pricing, or templates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clear context: this tool creates a cart for checkout, implying when to use it. However, it lacks explicit alternatives or when-not to use it, though sibling distinction is implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List the GridGarden Brick Premium modular components — middle and TOP planks in XS–XL sizes (plus a 1200mm XXL TOP) and the connector pin — with live EUR unit prices and availability from Shopify. Brick Premium only; no other materials are sold. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| catalog | Yes | |
| summary | Yes | |
| currency | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint and openWorldHint. The description adds that prices are live from Shopify and in EUR, and that the tool is read-only, consistent with annotations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences efficiently convey purpose, scope, and constraints. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool with no parameters, the description fully covers what it does, what it lists, and the source of data. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so schema coverage is 100%. Baseline is 4. Description does not need to add parameter info; it is complete for a zero-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool lists specific GridGarden Brick Premium components (planks and connector pin) with live prices and availability. It explicitly names the product line and components, distinguishing it from sibling tools like studio_pricing_quote.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description specifies that it is a read-only catalog for Brick Premium only, indicating when to use it. It implies not for other materials or pricing quotes, but does not explicitly state alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List the design-knowledge-base rules relevant to one step of designing a garden (brief / koncept / dispozicia / vysadba / materialy) — up to 20 rules, each with its predicate, numeric thresholds, strength (must/should/may), confidence tag, and cited sources. No garden scene is read or required; this is reference knowledge, not a check against a specific design. Deterministic: the same step always returns the same rule set.
| Name | Required | Description | Default |
|---|---|---|---|
| step | Yes | Design process step to fetch rules for: brief, koncept, dispozicia, vysadba, materialy. Call this once per step you are working on — do not assume one step's rules cover another. |
| Name | Required | Description |
|---|---|---|
| step | Yes | |
| rules | Yes | |
| total | Yes | |
| summary | Yes | |
| truncated | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry readOnlyHint=true and openWorldHint=false, and the description is consistent with both. It adds value beyond annotations by disclosing determinism ('the same step always returns the same rule set'), the reference-only nature ('No garden scene is read or required'), and the output structure (up to 20 rules with predicate, thresholds, strength, confidence, sources). No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three dense sentences with no filler. The main purpose is front-loaded, followed by the reference-not-check clarification and the determinism guarantee. Slightly more detail than strictly needed given the schema and annotations, but every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Complete for a single-parameter reference tool. The output schema covers the return format, annotations cover the read-only safety profile, and the description adds the determinism guarantee and the no-scene-required clarification. An agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the enum fully specifies the step values with descriptions, so the schema already does the heavy lifting. The tool description merely restates the step values and adds the 'one step at a time' constraint, which the schema description already conveys. Baseline 3 is appropriate when the schema covers all parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('List') and resource ('design-knowledge-base rules') scoped to a single design step, and enumerates the five valid steps (brief/koncept/dispozicia/vysadba/materialy). This clearly differentiates it from the sibling tools, which deal with BOM, catalog bricks, pricing, and templates — entirely different domains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clarifies this is reference knowledge, not a check against a specific garden scene, and the schema description adds explicit per-step guidance: 'Call this once per step you are working on — do not assume one step's rules cover another.' It gives clear usage context but does not explicitly name exclusions against alternatives; differentiation from siblings is implied via domain rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Compute the exact bill of materials (panels + connector pins) and total EUR price for a GridGarden modular Brick Premium raised bed (rectangle / L / U) or freestanding wall, from dimensions in millimetres. Quantities come from the same engine as the Studio configurator; prices are read live from Shopify for the delivery market you pass in country.
| Name | Required | Description | Default |
|---|---|---|---|
| shape | Yes | Design type and the dimension fields it needs (all in mm, auto-snapped to the 60mm build grid): rectangle → length + width; lshape → length1 + width1 + length2 + width2; ushape → topLength + topWidth + arm1Length + arm1Width + arm2Length + arm2Width; wall → wallLength. Layers: raised beds 2–13, walls 1–25. Call studio_templates_list for ready example dimensions. | |
| width | No | Rectangle: outer width in mm. | |
| layers | Yes | Number of brick layers. Raised beds 2-13, walls 1-25 (1 = a single 60mm top-cap course). Each layer ≈120mm tall (top layer +60mm). | |
| length | No | Rectangle: outer length in mm. | |
| width1 | No | L-shape: first leg width in mm. | |
| width2 | No | L-shape: second leg width in mm. | |
| country | No | Delivery market as an ISO-3166-1 alpha-2 code (e.g. "DE", "AT", "SK"). Prices differ by market: SK and CZ are base, every other EU market adds €1 per structural piece. Ask which country the order ships to; omit only if unknown — that returns base (SK/CZ) prices. | |
| length1 | No | L-shape: first leg length in mm. | |
| length2 | No | L-shape: second leg length in mm. | |
| topWidth | No | U-shape: back (top) width in mm. | |
| arm1Width | No | U-shape: arm 1 width in mm. | |
| arm2Width | No | U-shape: arm 2 width in mm. | |
| topLength | No | U-shape: back (top) length in mm. | |
| arm1Length | No | U-shape: arm 1 length in mm. | |
| arm2Length | No | U-shape: arm 2 length in mm. | |
| wallLength | No | Wall: single straight segment length in mm. |
| Name | Required | Description |
|---|---|---|
| bom | Yes | |
| shape | Yes | |
| layers | Yes | |
| country | Yes | |
| snapped | No | |
| summary | Yes | |
| currency | Yes | |
| total_eur | Yes | |
| editor_url | Yes | |
| price_basis | Yes | |
| shopify_items | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral details beyond annotations: quantities come from the same engine as the Studio configurator, prices are read live from Shopify, the build grid auto-snaps to 60mm, and the per-market surcharge depends on the `country` parameter. This goes beyond what the annotation alone provides, though it does not mention output structure (covered by output schema) or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is exactly two sentences. The first sentence front-loads the verb, resource, and scope; the second adds two important behavioral facts (same engine as configurator, live Shopify prices by country). No filler, no tautology—every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having 16 parameters, the combination of a rich schema, output schema, and annotations already covers most of the burden. The description supplies the overarching context: what the tool computes, where the numbers come from, how pricing varies by market, and the grid snapping behavior. It also offloads template examples to a sibling tool. The tool is fully understood for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is fully self-descriptive (100% coverage) with detailed descriptions for every parameter, including shape-specific fields, layer limits, and country rules. The tool description itself adds little to parameter understanding—it restates the engine and live pricing context but does not need to, because the schema already explains each field thoroughly. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb ('Compute') and names the exact resource: bill of materials (panels + connector pins) and total EUR price. It also enumerates the product family (GridGarden modular Brick Premium raised bed rectangle/L/U or freestanding wall) and input dimensions in millimetres, clearly distinguishing it from sibling tools like studio_bom_to_cart (cart operation) or studio_templates_list (templates).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use this tool (to get a quote/BOM from dimensions) and even directs users to studio_templates_list for ready example dimensions in the shape parameter. It does not explicitly state 'use studio_catalog_bricks for product info' or exclude when not to use it, but the context is enough to avoid confusion among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List the design shapes GridGarden Studio supports, with the dimension parameters each one needs.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| templates | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the description confirms a read operation. It adds that the tool lists shapes and dimension parameters, but no further behavioral details are needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, clear sentence that conveys the purpose without any extraneous information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and an output schema present, the description fully covers the tool's functionality. It explains what the tool does and what the response includes.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so baseline is 4. The description adds value by explaining what the output will contain (shapes and dimension parameters), though schema coverage is 100%.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it lists design shapes and their dimension parameters. The sibling tools involve BOM, catalog bricks, and pricing quotes, so this tool is distinctly about template listing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving supported shapes, but does not explicitly state when to avoid it or contrast with siblings. However, the context of sibling tools makes the usage clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
studio_design_rulesstudio_bom_to_cart3 fields changedInput schema / properties / countryAdded value: +{
+ "description": "Delivery market as an ISO-3166-1 alpha-2 code (e.g. \"DE\", \"AT\", \"SK\"). Prices differ by market: SK and CZ are base, every other EU market adds €1 per structural piece. Ask which country the order ships to; omit only if unknown — that returns base (SK/CZ) prices.",
+ "maxLength": 2,
+ "minLength": 2,
+ "type": "string"
+}Output schema / properties / price_basisAdded value: +{
+ "const": "shopify_cart",
+ "type": "string"
+}Output schema / requiredPrevious value: -[
- "checkout_url",
- "cart_id",
- "total_eur",
- "total_quantity",
- "currency",
- "line_items",
- "summary",
- "editor_url"
-]New value: +[
+ "checkout_url",
+ "cart_id",
+ "total_eur",
+ "total_quantity",
+ "currency",
+ "price_basis",
+ "line_items",
+ "summary",
+ "editor_url"
+]studio_pricing_quote4 fields changedInput schema / properties / countryAdded value: +{
+ "description": "Delivery market as an ISO-3166-1 alpha-2 code (e.g. \"DE\", \"AT\", \"SK\"). Prices differ by market: SK and CZ are base, every other EU market adds €1 per structural piece. Ask which country the order ships to; omit only if unknown — that returns base (SK/CZ) prices.",
+ "maxLength": 2,
+ "minLength": 2,
+ "type": "string"
+}Output schema / properties / countryAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / price_basisAdded value: +{
+ "const": "shopify_live",
+ "type": "string"
+}Output schema / requiredPrevious value: -[
- "shape",
- "layers",
- "bom",
- "shopify_items",
- "total_eur",
- "currency",
- "summary",
- "editor_url"
-]New value: +[
+ "shape",
+ "layers",
+ "bom",
+ "shopify_items",
+ "total_eur",
+ "currency",
+ "country",
+ "price_basis",
+ "summary",
+ "editor_url"
+]studio_bom_to_cartstudio_catalog_bricksstudio_pricing_quotestudio_templates_listInstant parametric cost estimates for custom manufacturing: CNC, molding, sheet metal, 3DP, PCB.
Turn designs into shipped parts: quote 3D printing, CNC, and decals, then check out.
Search crops, check companion planting, explore seasonal calendars, and find planting plans.
Construction takeoff and estimating for AI agents. Measure a drawing PDF, export a priced estimate.
Add one secure layer between your agents and this server.
