Skip to main content
Glama

Add Fastener

add_fastener

Add a standard ISO metric screw, bolt, nut, or washer as a solid, specifying size, length, grade, and placement for mechanical assemblies.

Instructions

Add a standard ISO metric fastener (screw / bolt / nut / washer) as a solid.

kind: one of "socket_head_cap_screw", "hex_bolt", "hex_nut", "washer".

  • socket_head_cap_screw: cylindrical head with a cosmetic hex socket + plain shank (threads not modeled).

  • hex_bolt: hex head (across-flats) + plain shank.

  • hex_nut: hex prism with an axial clearance hole.

  • washer: flat annular ring. size: ISO designation, one of "M3","M4","M5","M6","M8","M10","M12". length: shank length in mm. REQUIRED for socket_head_cap_screw and hex_bolt; ignored for nut/washer. grade: optional material / property class AS ORDERED — ISO 898-1 for steel screws ("8.8", "12.9"), ISO 898-2 for nuts ("8", "10"), ISO 3506 for stainless ("A2", "A4-80"). It changes no geometry. What it changes is the ORDERABLE designation stamped on the part: with it you get "ISO 4762 M4×12 A2", which a buyer can quote; without it the designation comes back complete=False saying nobody has chosen between class 8.8 steel and A2 stainless yet. An unrecognised grade is a loud error, never a guess. placement: optional [x, y, z] mm translation of the fastener origin (head top sits at z=0, shank runs in -z for screws/bolts). name: optional object name (default derived from kind).

All dimensions are in mm. Threads are cosmetic (the shank is a plain cylinder of the major diameter).

Returns {handle, name, kind, size, major_diameter, pitch, volume, designation, orderable} plus, by kind: screws/bolts add {length, head_diameter, head_height, model_thread:false}; nut adds {head_diameter (wrench across-flats), head_height}; washer adds {head_diameter (outer diameter), head_height (thickness)}. Mating numbers: drill a through-hole of major_diameter (+ clearance) for the shank; head_diameter sizes a counterbore. designation is the canonical orderable identity ("ISO 4762 M4×12 A2") and orderable its full card. catalog is the off-the-shelf verdict computed at creation time — code stocked, or not_stocked naming the lengths either side. A length nobody stocks is a FINDING, not a refusal: the solid is still built, so you can decide whether to move the stack-up or accept a special.

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": {
      "kind": "<kind>",
      "size": "<size>"
    },
    "name": "add_fastener"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameNo
sizeYes
gradeNo
lengthNo
placementNo
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as a non-destructive, non-read-only, closed-world mutation, and the description adds substantial behavior beyond that: threads are cosmetic (plain cylinder of major diameter), grade changes no geometry, an unrecognised grade is a loud error rather than a guess, and an unstocked length still builds the solid. These are exactly the non-obvious traits an agent needs before calling.

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?

Long but well-structured as a per-parameter breakdown followed by return shape and mating guidance; the density earns its place. A few phrases are padded ('What it changes is the ORDERABLE designation stamped on the part') and could be tightened without losing meaning.

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

Completeness5/5

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

Despite having no output schema, the description spells out the return payload ({handle, name, kind, size, major_diameter, pitch, volume, designation, orderable}) plus per-kind additions and what designation/orderable/catalog mean. For a 7-parameter generator tool, nothing an agent needs to call or interpret the result is missing.

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

Parameters5/5

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

Schema coverage is only 14%, so the description must carry the parameters, and it does: it enumerates the four allowed kind values with per-kind geometry notes, lists the valid size designations, specifies length's conditional requirement, defines placement's origin convention (head top at z=0, shank in -z), and explains grade's exact semantics. Only `workspace` is left to the schema, and its own description covers it.

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 specific verb and resource ('Add a standard ISO metric fastener ... as a solid') and immediately enumerates the four kinds, which cleanly separates it from sibling part generators like add_gear, add_bearing, and add_spring. An agent knows exactly what class of object this produces.

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 operational context: length is required for screws/bolts and ignored for nut/washer, grade is optional and only affects the orderable designation, and catalog misses are findings rather than refusals. It also explains downstream use (drill a through-hole of major_diameter, head_diameter sizes a counterbore). It does not name explicit alternatives, but the when-to-use picture is unambiguous.

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

Deploy Server

Other Tools