Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_fastener

Create standard ISO metric fasteners — socket head cap screws, hex bolts, nuts, or washers — as solid models with orderable designations and stock-length catalog checks.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
nameNo
sizeYes
gradeNo
lengthNo
placementNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discharges it: threads are cosmetic (plain cylinder of major diameter), grade changes no geometry but affects the orderable designation, an unrecognised grade is a loud error and never a guess, and an unstocked length is a FINDING rather than a refusal (solid still built). These are exactly the non-obvious traits an agent needs.

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?

Purpose is front-loaded and the kind list is cleanly bulleted, with almost no filler. It is long, but the density is warranted for a geometrically complex parametric tool; a couple of meta-remarks (e.g. the orderable/grade explanation) run slightly long.

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?

For a 6-parameter tool with no output schema and no annotations, the description supplies everything needed: units, threading caveat, minimum hole/counterbore mating numbers, and a full return-shape breakdown (handle, designation, orderable, catalog, per-kind fields). Nothing essential 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 description coverage is 0%, so the description must compensate, and it does: kind is enumerated with per-kind geometry notes, size is an explicit ISO list (M3–M12), length's requiredness is conditioned by kind, grade defines the three ISO standard families, and placement defines the origin convention (head top at z=0, shank in -z). Each parameter gains meaning beyond the bare schema.

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?

Opens with a specific verb+resource ('Add a standard ISO metric fastener ... as a solid') and immediately enumerates the four supported kinds, letting an agent distinguish this from siblings like add_bearing or add_gear without opening the schema. The scope and output artifact are unambiguous.

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 conditional guidance: length is REQUIRED for socket_head_cap_screw/hex_bolt and ignored for nut/washer, and grade is optional. It contextualizes the catalog/orderable verdict as a decision aid (move the stack-up vs accept a special), but does not explicitly route the agent to siblings such as standard_part_designate or catalog_search when off-the-shelf matching is the goal.

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