Skip to main content
Glama

Standard Part Designate

standard_part_designate
Read-only

Generates canonical, orderable designations for purchased standard parts from handles, strings, or family/spec facts, turning ambiguous BOM rows into quotable part numbers.

Instructions

The canonical, orderable designation of a purchased standard part — the string a buyer can actually quote against: "ISO 4762 M4×12 A2", "608-2RS", "AS568-214 NBR70". A BOM row that reads "SocketHeadCapScrew" is not a buyable line; this is what turns it into one.

Three ways in: handle read the designation add_fastener / add_bearing / add_thread stamped on the part when it was built. An object with no stamp reports designation=None plus whether its NAME reads like a purchased part. Nothing is ever inferred from geometry, so a hand-modelled bracket cannot acquire a false designation. designation normalise/parse a string — 'iso4762 m4x12 a2' becomes 'ISO 4762 M4×12 A2', so two spellings of one part can never become two BOM lines. family+spec build one from facts. family is fastener | bearing | oring | threaded_rod, and spec is respectively {kind, size, length, grade} / {designation, seals} / {inner_diameter, cross_section, compound} / {diameter, pitch, length, grade}.

Offline and deterministic — no network, no supplier, no credentials.

Returns the designation card: {ok, family, standard, designation, complete, reason, purchased, ...family-specific fields}. complete=False means the string is not yet enough to order against (typically nobody said which material grade), with reason naming the gap — a missing fact is reported, never defaulted to a plausible-looking lie.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "standard_part_designate"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNo
familyNo
handleNo
workspaceNoRun this call in this named workspace
designationNo

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with 'Offline and deterministic — no network, no supplier, no credentials.' Beyond that it adds genuinely useful behavior: no inference from geometry (so hand-modelled parts cannot acquire a false designation), and complete=False with `reason` rather than a defaulted plausible value. It stops short of describing failure behavior for invalid family or empty input.

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 and the buyer-quotable framing are front-loaded, and the three input modes are cleanly enumerated. A few phrases are rhetorical rather than informational ('never defaulted to a plausible-looking lie'), but the overall density is high and nearly every sentence carries operational meaning.

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?

With no output schema, the description correctly documents the returned designation card ({ok, family, standard, designation, complete, reason, purchased, ...}) and the semantics of complete=False. The remaining gap is the zero-required-parameter case: an agent cannot tell from the description what an empty call returns or which mode wins when inputs are combined.

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 only 20% (only `workspace` is documented), so the description must carry the load — and it does, explaining that handle reads a stamp, designation parses/normalises a string ('iso4762 m4x12 a2' → 'ISO 4762 M4×12 A2'), and family+spec builds from facts with the exact spec shape enumerated for fastener, bearing, oring, and threaded_rod. This is far more than the schema provides.

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?

The description states a specific verb and resource — producing the canonical, orderable designation string for a purchased standard part — and grounds it with concrete examples ('ISO 4762 M4×12 A2', '608-2RS') plus the non-goal ('a BOM row that reads SocketHeadCapScrew is not a buyable line'). It also distinguishes itself from the geometry-building siblings by explaining that stamps come from add_fastener/add_bearing/add_thread and that nothing is inferred from geometry, so an agent can tell it apart from catalog_search, designation_check, or the add_* tools.

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?

The 'Three ways in' block gives explicit context for each mode: handle for stamped parts, designation for normalising a string, family+spec for building from facts, with per-family spec shapes. What is missing is precedence — all five params are optional, and the description never says what happens if several are supplied or if none is, nor does it point to designation_check or catalog_search as alternatives for other needs.

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