Extrabold Tools Gridfinity

Generate Gridfinity Drawer Baseplate

generate_gridfinity_drawer_baseplate

Generate a Gridfinity baseplate sized to a known drawer preset. Supply measured drawer dimensions when available and the printer build volume; the tool automatically enables build-plate splitting when the baseplate does not fit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version`	No		0.5.21
`tolerance`	No		standard
`linkOrigin`	No		mcp
`marginType`	No		solid
`borderRadius`	No
`magnetHeight`	No
`baseplateType`	No		normal
`gridUnitDepth`	No
`gridUnitWidth`	No
`plateMarginMm`	No
`screwHeadSize`	No
`screwHoleSize`	No
`splitStrategy`	No		fewerParts
`toggleMagnets`	No
`drawerPresetId`	Yes	Exact preset id returned by find_gridfinity_drawer_presets.
`magnetDiameter`	No
`partsConnector`	No		none
`magnetDirection`	No		top
`magnetHoleStyle`	No		cylinder
`splitOffMargins`	No	Create outer margins as separate strips while keeping corners attached to top or bottom strips.
`toggleScrewHoles`	No
`measuredDimensions`	No	Measured drawer interior dimensions in millimeters. These override the approximate preset dimensions.
`printerBuildVolume`	Yes	The printer build volume used to decide whether this drawer-sized baseplate must be split.
`splitToBuildplates`	No	Override the automatic printer-fit split decision.
`removeHolesOnSplitLines`	No
`toggleMagnetReleaseHole`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It does mention that it automatically enables build-plate splitting when the baseplate does not fit, which is a key behavior. However, it does not disclose what the tool returns, whether it writes files, or any side effects or permissions needed, leaving significant gaps.

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?

The description is two sentences, concise and front-loaded with the core action. It earns its place by conveying the key purpose and the auto-splitting behavior. However, given the tool's complexity, a slightly longer description could be justified without violating conciseness.

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?

This is a complex tool with 26 parameters, nested objects, and no output schema. The description covers only the high-level idea and a single behavioral trait (splitting). It does not explain how outputs are returned, what the default values imply, or how the many optional parameters affect the result, making it incomplete for an AI agent.

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 19%, so the description must compensate. It adds context for drawerPresetId, measuredDimensions, and printerBuildVolume, but the other 20+ parameters (e.g., tolerance, baseplateType, magnet settings) are left unexplained in both schema and description. For a tool with 26 parameters, this is insufficient guidance for correct invocation.

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 states a specific verb ('Generate') and resource ('Gridfinity baseplate') with clear scope ('sized to a known drawer preset'). It also distinguishes itself from sibling tools by focusing on drawer-based generation and automatic splitting, whereas siblings like create_gridfinity_baseplate_url or generate_gridfinity_grid serve different purposes.

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 tool when you have a known drawer preset, supply measured dimensions and printer build volume, and it automatically handles splitting. It does not explicitly mention alternatives or when not to use, but the context is sufficient for an AI to select it appropriately given the sibling list.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0

Disambiguation3/5

Some overlap exists between create_gridfinity_baseplate_url and generate_gridfinity_grid, as both produce shareable URLs. However, the cross-reference in descriptions helps clarify that one is for exact settings and the other for row/column grids. The remaining tools are distinct in purpose.

Naming Consistency4/5

All tool names follow a consistent snake_case pattern with a verb (create, find, generate, get) followed by 'gridfinity' and a specific object. The main inconsistency is the use of both 'create' and 'generate' for similar actions, but the pattern is otherwise predictable.

Tool Count5/5

With just 5 tools, the server is well-scoped for its specific purpose of Gridfinity baseplate generation. Each tool covers a distinct need without unnecessary bloat, fitting comfortably within the ideal 3-15 range.

Completeness4/5

The tool set covers the core workflow: finding presets, generating baseplates from presets or grids, creating URLs, and guiding configuration. Minor gaps exist, such as no direct conversion between exact dimensions and grid counts, but these can be worked around with existing tools.

Resources

Need Help?