Extrabold Tools Gridfinity

Generate Gridfinity Grid

generate_gridfinity_grid

Generate a Gridfinity baseplate grid by columns and rows, returning the calculated millimeter dimensions and a shareable Extrabold Tools URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes	Number of Gridfinity rows across the depth.
`columns`	Yes	Number of Gridfinity columns across the width.
`version`	No		0.5.21
`tolerance`	No		standard
`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
`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		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
`printerBuildVolume`	No
`splitToBuildplates`	No	Override automatic printer-fit splitting. When omitted with a printer build volume, splitting is enabled only when needed.
`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.

Changed2 schema fields changedAug 12, 2026

addedInput schema / properties / splitOffMargins

Added value: +{
+  "default": false,
+  "description": "Create outer margins as separate strips while keeping corners attached to top or bottom strips.",
+  "type": "boolean"
+}

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

First observedAug 5, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool calculates dimensions and returns a URL, but does not mention side effects, error handling, network calls for URL generation, or any constraints on inputs. The behavior is not deeply transparent.

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 a single sentence that efficiently communicates the core function and expected outputs. It is front-loaded with the action and resource, and no space is wasted on redundant information.

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?

Given the tool has 26 parameters, a nested object, and no output schema, a one-sentence description is insufficient for an agent to fully understand invocation context. The description omits important configuration details, such as how printerBuildVolume affects splitting or what results the URL provides, making it incomplete for the tool's complexity.

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?

Schema description coverage is only 62%, so the description should help explain parameters beyond the schema. However, the description only mentions columns and rows, which are already documented in the schema. It does not add meaning for the many other parameters like tolerance, baseplateType, or printerBuildVolume, nor does it clarify the output dimensions calculation.

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?

The description clearly states the tool generates a Gridfinity baseplate grid based on columns and rows, and specifies the return values (millimeter dimensions and a shareable URL). This makes the primary purpose clear, though it does not explicitly differentiate itself from the sibling tools like create_gridfinity_baseplate_url or generate_gridfinity_drawer_baseplate.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus the sibling tools, nor does it mention prerequisites, limitations, or alternative scenarios. There is no indication of when columns/rows generation is preferred over other grid-related tools.

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?