Extrabold Tools Gridfinity

Create Gridfinity Baseplate URL

create_gridfinity_baseplate_url

Read-onlyIdempotent

Create a shareable Extrabold Tools Gridfinity baseplate URL from exact baseplate settings. Use generate_gridfinity_grid when the user asks for a grid by rows and columns.

Input Schema

Name	Required	Description	Default
`printer`	No
`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
`topCutoff`	No
`dimensions`	No
`linkOrigin`	No	Link origin tag added as the org query parameter for attribution.	mcp
`marginType`	No		solid
`sizingMode`	No		direct
`borderRadius`	No
`magnetHeight`	No
`showAdvanced`	No
`baseplateType`	No		normal
`bottomChamfer`	No
`bottomPadding`	No
`gridAlignment`	No
`gridUnitDepth`	No
`gridUnitWidth`	No
`plateMarginMm`	No
`screwHeadSize`	No
`screwHoleSize`	No
`splitStrategy`	No		fewerParts
`toggleMagnets`	No
`magnetDiameter`	No
`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
`pieceSpacingMm`	No
`advancedWarning`	No
`magnetDirection`	No		top
`magnetHoleStyle`	No		cylinder
`splitOffMargins`	No
`magnetBaseHeight`	No
`toggleScrewHoles`	No
`containerPresetId`	No
`outerBorderRadius`	No
`edgeConnectorSides`	No
`enablePlateNesting`	No
`splitToBuildplates`	No
`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
`toggleMagnetReleaseHole`	No
`overrideMaxOuterBorderRadius`	No

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"
```

Changed2 schema fields changedAug 12, 2026
- addedInput schema / properties / splitOffMargins
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
- changedInput schema / properties / version / default
```
Previous value: -"0.5.20"New value: +"0.5.21"
```
First observedAug 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that the URL is 'shareable' and derived from exact settings; it does not say whether anything is uploaded or persisted, whether the URL is stateless, or how it round-trips settings. Adequate but thin given the annotation coverage.

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?

Two short sentences, front-loaded with the core action and followed by a routing cue, with no filler. It is appropriately sized, though the second sentence spends its budget on only one alternative rather than the most relevant one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 41-parameter, nested-object tool with no output schema and 10% schema coverage needs far more explanation of inputs and of what the produced URL contains. The description omits parameter guidance entirely and does not state the return value (a URL string) or its relationship to the sibling generator tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 41 parameters at only 10% schema description coverage, the description must carry the explanatory burden, and it does not: it says only 'exact baseplate settings' without explaining any parameter groups, units, or the printer/tolerance implications. The phrase 'exact settings' does hint at full-fidelity round-tripping, which is marginally useful, but the vast parameter surface is undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (create a shareable Gridfinity baseplate URL) and the input basis (exact baseplate settings), which is clearly distinct from a generator that outputs geometry. It names one sibling and the condition for it, but oddly routes to generate_gridfinity_grid rather than the more closely related generate_gridfinity_baseplate, leaving some ambiguity about which generating tool this URL complements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides one explicit routing rule: use generate_gridfinity_grid when the user asks for a grid by rows and columns. However, it never clarifies when to prefer this URL tool over generate_gridfinity_baseplate, which presumably consumes the same settings, so the primary selection decision is left inferred.

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?