Extrabold Tools Gridfinity

Generate Gridfinity Baseplate from Measurements

generate_gridfinity_baseplate

Read-onlyIdempotent

Configure a Gridfinity baseplate from exact width and depth in millimeters, without a drawer preset. Returns the full-unit grid, leftover margins, printer fit, warnings, and a website URL. Supply printerBuildVolume from find_gridfinity_printers to enable automatic splitting.

Input Schema

Name	Required	Description	Default
`version`	No		5.3
`tolerance`	No	Experimental fit setting saved per printer. For dovetails, 0 mm gives the largest male tab; higher values make it smaller, up to 0.5 mm. Also affects CLICKbase clips and magnet holes. Print the tolerance test package to choose a dovetail fit. Normal bin pockets keep fixed geometry; the included bin-fit sample is a reference check. Values: none = 0 mm, tight = 0.1 mm, standard = 0.2 mm, loose = 0.3 mm, very-loose = 0.4 mm, extra-loose = 0.5 mm.	standard
`dimensions`	Yes	Measured interior or desired baseplate width and depth in millimeters.
`linkOrigin`	No	Link origin tag added as the org query parameter for attribution.	mcp
`marginType`	No		solid
`borderRadius`	No
`magnetHeight`	No	Height or thickness of the magnets in millimeters.
`baseplateType`	No	Baseplate style to generate.	normal
`gridAlignment`	No
`gridUnitDepth`	No	Depth of one grid unit in millimeters. Standard Gridfinity uses 42.
`gridUnitWidth`	No	Width of one grid unit in millimeters. Standard Gridfinity uses 42.
`plateMarginMm`	No
`screwHeadSize`	No	Diameter of the screw head in millimeters.
`screwHoleSize`	No	Diameter of the screw shaft in millimeters.
`splitStrategy`	No		fewerParts
`toggleMagnets`	No
`magnetDiameter`	No	Diameter of the magnets in millimeters.
`partsConnector`	No	Experimental dovetails interlock split pieces without separate parts and use your printer tolerance for male tabs. They require Split to Build Plates and work with all baseplate types. Clips connect split seams and optional outer edges; the printable clip model is included (not compatible with Skeleton).	none
`magnetDirection`	No	Which side of the baseplate magnets are inserted from.	top
`magnetHoleStyle`	No	Round holes are sized with the magnet diameter. Crush ribs use a wavy profile with flexible ribs that grip the magnet.	cylinder
`splitOffMargins`	No	Create outer margins as separate strips while keeping corners attached to top or bottom strips.
`toggleScrewHoles`	No
`edgeConnectorSides`	No
`printerBuildVolume`	No
`splitToBuildplates`	No	Override automatic printer-fit splitting. When omitted with a printer build volume, splitting is enabled only when needed.
`enableEdgeConnectors`	No
`connectMarginCrossings`	No	Also place a dovetail wherever a split edge crosses from grid cells into a margin region. Off: dovetails only at cell-to-cell crossings.
`removeHolesOnSplitLines`	No	Remove screw holes that fall on split edges.
`toggleMagnetReleaseHole`	No	Add through-holes so magnets can be pushed back out from the opposite side.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 8, 2026

addedInput schema / properties / connectMarginCrossings

Added value: +{
+  "default": true,
+  "description": "Also place a dovetail wherever a split edge crosses from grid cells into a margin region. Off: dovetails only at cell-to-cell crossings.",
+  "type": "boolean"
+}

addedInput schema / properties / partsConnector / description

Added value: +"Experimental dovetails interlock split pieces without separate parts and use your printer tolerance for male tabs. They require Split to Build Plates and work with all baseplate types. Clips connect split seams and optional outer edges; the printable clip model is included (not compatible with Skeleton)."

addedInput schema / properties / tolerance / description

Added value: +"Experimental fit setting saved per printer. For dovetails, 0 mm gives the largest male tab; higher values make it smaller, up to 0.5 mm. Also affects CLICKbase clips and magnet holes. Print the tolerance test package to choose a dovetail fit. Normal bin pockets keep fixed geometry; the included bin-fit sample is a reference check. Values: none = 0 mm, tight = 0.1 mm, standard = 0.2 mm, loose = 0.3 mm, very-loose = 0.4 mm, extra-loose = 0.5 mm."

changedInput schema / properties / version / default
```
Previous value: -"0.5.21"New value: +"5.3"
```

AddedOct 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: it enumerates what is returned (full-unit grid, leftover margins, printer fit, warnings, URL) and explains the conditional splitting trigger tied to printerBuildVolume. It stops short of covering validation failures or the meaning of warnings.

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, no filler. The core scope constraint is front-loaded in the first sentence, output contents second, and the key cross-tool input hint third. Every sentence carries information an agent needs.

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?

For a 29-parameter, nested-object tool with no output schema, the description usefully summarizes the return payload and the splitting behavior, which is the highest-value missing context. It is not exhaustive about the many optional connector/magnet/split flags, but those are documented in the schema itself.

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 description coverage is 62%, above the baseline threshold, and the schema already documents the non-obvious parameters (tolerance, partsConnector, magnetHoleStyle, connectMarginCrossings). The description only adds meaning for dimensions and printerBuildVolume; for a 29-parameter tool the remaining gap in schema coverage is not compensated in prose. Baseline 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?

States a specific verb (Configure/Generate) plus resource (Gridfinity baseplate) and immediately scopes it: 'from exact width and depth in millimeters, without a drawer preset.' The phrase 'without a drawer preset' explicitly distinguishes it from the sibling generate_gridfinity_drawer_baseplate, so an agent can route correctly without opening schemas.

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?

Gives clear context: use this when you have raw width/depth measurements rather than a drawer preset, and it names the upstream dependency ('Supply printerBuildVolume from find_gridfinity_printers to enable automatic splitting'). It does not explicitly state when to prefer create_gridfinity_baseplate_url or the drawer variant, so it falls short of a full when/when-not/alternatives statement.

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

All Extrabold Tools Gridfinity 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?