A
licenseNot graded
qualityC
maintenancePlan optimal container & truck loads: 3D layouts, right-size the container mix, and check utilization, centre of gravity, crush protection and securing across 200+ equipment types.
16
MIT
studio
Server Details
Design & price modular raised garden beds and walls: exact bill of materials, EUR price + checkout.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
4 toolsstudio_bom_to_cartAdd a GridGarden design to a Shopify cart (checkout link)ADestructiveInspect
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.
ParametersJSON Schema
| 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. |
Output Schema
ParametersJSON Schema
| 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 |
TDQS
A4.5/5.0
Behavior5/5
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.
Conciseness5/5
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.
Completeness5/5
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.
Parameters3/5
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.
Purpose5/5
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.
Usage Guidelines4/5
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.
studio_catalog_bricksGridGarden Brick Premium catalog + live pricesARead-onlyInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| catalog | Yes | |
| summary | Yes | |
| currency | Yes |
TDQS
A4.5/5.0
Behavior4/5
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.
Conciseness5/5
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.
Completeness5/5
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.
Parameters4/5
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.
Purpose5/5
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.
Usage Guidelines4/5
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.
studio_pricing_quoteGridGarden raised-bed / wall price quoteARead-onlyInspect
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.
ParametersJSON Schema
| 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. |
Output Schema
ParametersJSON Schema
| 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 |
TDQS
A4.3/5.0
Behavior4/5
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.
Conciseness5/5
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.
Completeness5/5
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.
Parameters3/5
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.
Purpose5/5
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.
Usage Guidelines4/5
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.
studio_templates_listGridGarden Studio templatesARead-onlyInspect
List the design shapes GridGarden Studio supports, with the dimension parameters each one needs.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| templates | Yes |
TDQS
A4.3/5.0
Behavior3/5
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.
Conciseness5/5
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.
Completeness5/5
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.
Parameters4/5
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.
Purpose5/5
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.
Usage Guidelines4/5
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.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Instant 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.
Related MCP Servers
@getfacade/mcpofficial
AlicenseAqualityBmaintenanceEnables an AI agent to create a building from a photo, generate a facade design, and order a line-by-line cost estimate and documentation album, using country-specific materials and construction norms.213331MIT- AlicenseAqualityCmaintenanceCalculates 3D printing cost, time, material weight and build-plate fit from plain dimensions given in the conversation, with no STL upload and no API key. Covers PLA, PETG, ABS, ASA, TPU, Nylon, PC and PLA-CF, plus build volumes for Bambu Lab, Prusa, Creality, Voron and Elegoo printers.3MIT
laguna-pools-mcpofficial
AlicenseNot gradedqualityDmaintenanceAI sales manager for composite swimming pools. Recommends pools by plot size & budget, calculates total cost with accessories, provides BIM/CAD files for architects, and connects clients with dealers across 175 Russian citiesMIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.3/5.0
Disambiguation4/5
Most tools have clearly distinct roles: listing templates, listing products, computing a price, and creating a cart. The only potential confusion is between studio_pricing_quote and studio_bom_to_cart, but their descriptions clarify that one returns a quote while the other builds a cart.
Naming Consistency2/5
All tools share the 'studio_' prefix, but the naming conventions vary: 'bom_to_cart' uses a phrase with 'to', while 'catalog_bricks', 'pricing_quote', and 'templates_list' mix noun-noun and gerund-noun patterns. There is no consistent verb_noun structure.
Tool Count5/5
With exactly 4 tools, the set is tightly scoped to the server's purpose: exploring designs, seeing available components, calculating prices, and initiating a purchase. Each tool adds distinct value and none feel redundant.
Completeness5/5
The tools cover the full user journey from template discovery to final checkout, including product catalog access and pricing. No obvious missing operations are needed for the stated domain of configuring and ordering GridGarden Brick Premium beds.