Extrabold Tools Gridfinity

Create Gridfinity Baseplate URL

create_gridfinity_baseplate_url

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

TableJSON Schema

Name	Required	Description	Default
`printer`	No
`version`	No		0.5.21
`tolerance`	No		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		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
`removeHolesOnSplitLines`	No
`toggleMagnetReleaseHole`	No
`overrideMaxOuterBorderRadius`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It states the outcome (a shareable URL) and input class (baseplate settings), but does not disclose whether any external call, validation, or side effect occurs. For a simple URL-creation tool this is acceptable but not rich.

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, front-loaded with the core action, and no filler. Every word earns its place.

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?

With 40 parameters, no output schema, and no annotations, the description is far too thin. It does not explain URL output format, default behavior, how to handle nested settings, or when to ask follow-up questions, so an agent cannot reliably populate a correct request.

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

Parameters1/5

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

Schema description coverage is only 3% across 40 parameters, and the description offers no per-parameter meaning beyond 'exact baseplate settings'. This vagueness does not help an agent map user requests to the nested objects (printer, dimensions, gridAlignment, edgeConnectorSides) or honor defaults.

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 uses a specific verb ('Create') and names the exact resource ('shareable Extrabold Tools Gridfinity baseplate URL') along with input ('exact baseplate settings'). It explicitly contrasts with generate_gridfinity_grid, satisfying sibling differentiation.

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 tells when to prefer generate_gridfinity_grid ('when the user asks for a grid by rows and columns'). It does not mention other siblings like generate_gridfinity_drawer_baseplate or get_gridfinity_grid_questions, so the guidance is helpful but incomplete.

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?