Skip to main content
Glama

Extrabold Tools Gridfinity

Generate Gridfinity Grid

generate_gridfinity_grid
Read-onlyIdempotent

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

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": {
      "columns": "<columns>",
      "rows": "<rows>"
    },
    "name": "generate_gridfinity_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesNumber of Gridfinity rows across the depth.
columnsYesNumber of Gridfinity columns across the width.
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
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
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. Changed5 schema fields changed
    • addedInput schema / properties / edgeConnectorSides
      Added value: +{
      +  "default": {
      +    "back": true,
      +    "front": true,
      +    "left": true,
      +    "right": true
      +  },
      +  "properties": {
      +    "back": {
      +      "default": false,
      +      "type": "boolean"
      +    },
      +    "front": {
      +      "default": false,
      +      "type": "boolean"
      +    },
      +    "left": {
      +      "default": false,
      +      "type": "boolean"
      +    },
      +    "right": {
      +      "default": false,
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / enableEdgeConnectors
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / marginType / enum
      Added value: +[
      +  "solid",
      +  "margin-fit",
      +  "halfgrid",
      +  "overtile"
      +]
    • addedInput schema / properties / partsConnector / enum
      Added value: +[
      +  "none",
      +  "clips",
      +  "dovetails"
      +]
    • addedInput schema / properties / splitStrategy / enum
      Added value: +[
      +  "fewerParts",
      +  "balanced",
      +  "tJunctions"
      +]
  4. 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"
  5. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered and the description does not contradict it. However, the sole sentence discloses no behavior beyond the return payload — nothing about how splitting to build plates is triggered, how tolerance affects geometry, or that no model is actually produced by this call versus a URL.

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?

A single front-loaded sentence with no filler and the output described up front. It is efficient, though for a 30-parameter tool it is arguably too terse rather than appropriately sized.

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 30 parameters, nested objects, seven enums, experimental splitting and dovetail behavior, and no output schema, one sentence is far from sufficient. Key questions an agent would have — what exactly is returned, whether a printable file is produced, how splitToBuildplates interacts with printerBuildVolume — go unanswered.

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?

Schema description coverage is 67% across 30 parameters, with detailed enum documentation already present for tolerance, partsConnector, magnetHoleStyle, and baseplateType. The description only touches columns and rows (already documented in the schema) and adds no meaning for the remaining parameters, so the schema carries the load and the baseline 3 applies.

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 gives a specific verb ('Generate') and resource ('Gridfinity baseplate grid by columns and rows') and states the outputs (millimeter dimensions and a shareable URL). It is clear on its own, but it offers no differentiation from the closely named siblings generate_gridfinity_baseplate and create_gridfinity_baseplate_url, leaving overlap ambiguous.

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 never says when to use this tool versus generate_gridfinity_baseplate, generate_gridfinity_drawer_baseplate, or create_gridfinity_baseplate_url, nor any prerequisites or when-not to use it. With three similarly named generator siblings, this is a real gap rather than a minor omission.

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