Skip to main content
Glama

Extrabold Tools Gridfinity

Generate Gridfinity Drawer Baseplate

generate_gridfinity_drawer_baseplate
Read-onlyIdempotent

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drawerPresetId": "<drawerPresetId>",
      "printerBuildVolume": "<printerBuildVolume>"
    },
    "name": "generate_gridfinity_drawer_baseplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNo5.3
toleranceNoExperimental 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
linkOriginNomcp
marginTypeNosolid
borderRadiusNo
magnetHeightNo
previewThemeNoTheme of the fallback preview image. Pass "light" when the chat uses a light theme; defaults to dark.
baseplateTypeNonormal
gridUnitDepthNo
gridUnitWidthNo
plateMarginMmNo
screwHeadSizeNo
screwHoleSizeNo
splitStrategyNofewerParts
toggleMagnetsNo
drawerPresetIdYesExact preset id returned by find_gridfinity_drawer_presets.
magnetDiameterNo
partsConnectorNoExperimental 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
magnetDirectionNotop
magnetHoleStyleNocylinder
splitOffMarginsNoCreate outer margins as separate strips while keeping corners attached to top or bottom strips.
toggleScrewHolesNo
measuredDimensionsNoMeasured drawer interior dimensions in millimeters. These override the approximate preset dimensions.
printerBuildVolumeYesThe printer build volume used to decide whether this drawer-sized baseplate must be split.
splitToBuildplatesNoOverride the automatic printer-fit split decision.
connectMarginCrossingsNoAlso place a dovetail wherever a split edge crosses from grid cells into a margin region. Off: dovetails only at cell-to-cell crossings.
removeHolesOnSplitLinesNo
toggleMagnetReleaseHoleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / previewTheme
      Added value: +{
      +  "description": "Theme of the fallback preview image. Pass \"light\" when the chat uses a light theme; defaults to dark.",
      +  "enum": [
      +    "dark",
      +    "light"
      +  ],
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • 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"
  3. Changed2 schema fields changed
    • 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"
  4. First observed

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, so the safety profile needs no restating. The description adds real behavioral content: measured dimensions override preset dimensions and build-plate splitting is auto-enabled when the plate doesn't fit. It stays silent on return artifacts, preview output, and the consequences of the experimental tolerance/dovetail settings.

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 tight sentences with the core scope front-loaded ahead of the conditional input advice. No filler, though the second sentence blends usage guidance and behavior in a way that slightly buries the automatic-split rule.

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?

For a 28-parameter generator with nested objects and no output schema, the description is too thin: it never says what the tool returns (model file, download link, preview image), what units or formats the id must take, or how the experimental tolerance/dovetail settings interact. An agent could invoke it but not predict its output.

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 28 parameters and only 32% schema description coverage, the description should carry more semantic load, yet it only touches measuredDimensions (override behavior) and printerBuildVolume (split decision). The many undocumented flags — linkOrigin, marginType, splitStrategy, partsConnector options, magnet/screw toggles, splitOffMargins — get no added meaning here, leaving the majority of parameters opaque.

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 and resource ('Generate a Gridfinity baseplate') and narrows the scope to 'sized to a known drawer preset,' which separates it from the generic sibling generate_gridfinity_baseplate without naming it. An agent can identify the drawer-preset variant and the two driving inputs without opening the schema.

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?

Gives conditional input guidance ('supply measured drawer dimensions when available and the printer build volume') and explains automatic splitting behavior, but never names an alternative tool or states when NOT to use this one. The preset id's origin is only clarified inside the schema, not in the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources