Skip to main content
Glama

Extrabold Tools Gridfinity

Generate Gridfinity Baseplate from Measurements

generate_gridfinity_baseplate
Read-onlyIdempotent

Configure a Gridfinity baseplate from exact width and depth in millimeters, without a drawer preset. Returns the full-unit grid, leftover margins, printer fit, warnings, a website URL, and an in-chat 3D preview. Supply printerBuildVolume from find_gridfinity_printers to enable automatic splitting.

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": {
      "dimensions": "<dimensions>"
    },
    "name": "generate_gridfinity_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
dimensionsYesMeasured interior or desired baseplate width and depth in millimeters.
linkOriginNoLink origin tag added as the org query parameter for attribution.mcp
marginTypeNosolid
borderRadiusNo
magnetHeightNoHeight or thickness of the magnets in millimeters.
previewThemeNoTheme of the fallback preview image. Pass "light" when the chat uses a light theme; defaults to dark.
baseplateTypeNoBaseplate style to generate.normal
gridAlignmentNo
gridUnitDepthNoDepth of one grid unit in millimeters. Standard Gridfinity uses 42.
gridUnitWidthNoWidth of one grid unit in millimeters. Standard Gridfinity uses 42.
plateMarginMmNo
screwHeadSizeNoDiameter of the screw head in millimeters.
screwHoleSizeNoDiameter of the screw shaft in millimeters.
splitStrategyNofewerParts
toggleMagnetsNo
magnetDiameterNoDiameter of the magnets in millimeters.
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
magnetDirectionNoWhich side of the baseplate magnets are inserted from.top
magnetHoleStyleNoRound holes are sized with the magnet diameter. Crush ribs use a wavy profile with flexible ribs that grip the magnet.cylinder
splitOffMarginsNoCreate outer margins as separate strips while keeping corners attached to top or bottom strips.
toggleScrewHolesNo
edgeConnectorSidesNo
printerBuildVolumeNo
splitToBuildplatesNoOverride automatic printer-fit splitting. When omitted with a printer build volume, splitting is enabled only when needed.
enableEdgeConnectorsNo
connectMarginCrossingsNoAlso place a dovetail wherever a split edge crosses from grid cells into a margin region. Off: dovetails only at cell-to-cell crossings.
removeHolesOnSplitLinesNoRemove screw holes that fall on split edges.
toggleMagnetReleaseHoleNoAdd through-holes so magnets can be pushed back out from the opposite side.

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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond them: the outputs produced (full-unit grid, leftover margins, printer fit, warnings, URL, in-chat 3D preview) and the fact that splitting is gated on an external build-volume input.

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?

Three sentences, front-loaded with purpose, then outputs, then the one prerequisite call. No filler, no restatement of the tool name, and the most actionable dependency is placed last where it is easy to scan.

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

Completeness4/5

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

There is no output schema, so the description is right to enumerate what comes back (grid, margins, fit, warnings, URL, preview), which it does. It is slightly thin for a 30-parameter generator, leaving the agent to mine the schema for most configuration behavior, but nothing needed for a correct default call is missing.

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

Parameters3/5

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

With 30 parameters at 63% schema description coverage, the schema carries most of the burden and many enum/boolean switches (splitStrategy, partsConnector, magnet options) are unexplained in prose. The description adds genuine meaning only for two inputs: dimensions as exact mm measurements and printerBuildVolume's source and effect on splitting.

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?

States a concrete verb plus resource (configure a Gridfinity baseplate) and a scoping qualifier (from exact width/depth in millimeters, without a drawer preset). That qualifier distinguishes it from the drawer-preset sibling in the same family without the agent needing to compare schemas.

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 an explicit integration instruction: supply printerBuildVolume from find_gridfinity_printers to enable automatic splitting, which tells the agent the correct upstream call. It stops short of stating when not to use this tool (e.g. when a drawer preset exists or when a shareable URL alone is wanted).

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