Skip to main content
Glama

Designation Check

designation_check
Read-only

Checks BOM rows or assemblies to flag purchased parts that cannot be ordered due to missing or incomplete designations, such as absent material grades, before quoting or release.

Instructions

Gate: every purchased part on this assembly must be orderable.

Flags BOM rows a buyer cannot act on — a purchased standard part with no canonical designation, or one whose designation is missing a fact needed to order it (no material grade). Run it before quoting or releasing a package: a BOM whose purchased lines are geometry names silently pushes the sourcing work onto a human, once per revision.

Purchased-ness is EXACT for AnkusDrive-generated parts (the object carries a stamp) and a documented name heuristic for everything else — so a hand-modelled "Bracket" is never flagged, while a hand-modelled "M6Screw" is. Pass rows instead of assembly to check BOM rows you already hold.

Returns {ok, findings, purchased, designated, undesignated, incomplete, basis}; each finding carries part / count / code (no_designation | incomplete_designation) / certainty (stamped | name_heuristic) / reason. ok=False means the BOM cannot be ordered as it stands.

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": "designation_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNo
assemblyNo
recursiveNo
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.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond by disclosing the certainty model (exact via stamp for AnkusDrive-generated parts, documented name heuristic otherwise), the meaning of ok=False, and the finding codes. That is exactly the behavior an agent needs to interpret and trust the result.

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?

Front-loaded with the gate statement, then rationale, then caveat, then return shape — well ordered. A few clauses (the 'once per revision' aside) are editorial rather than operational, keeping it just short of maximally tight.

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?

With no output schema, the description enumerates the return keys {ok, findings, purchased, designated, undesignated, incomplete, basis} and the per-finding fields, and explains the ok=False semantics. Nothing material is missing for correct invocation and interpretation.

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

Parameters4/5

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

Schema coverage is 25%, so description must carry weight; it does for the key ambiguity, explaining `rows` vs `assembly` as interchangeable input modes. `recursive` and `workspace` remain unexplained beyond the brief schema note, leaving a gap.

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+resource: it gates an assembly by flagging purchased BOM rows that lack a canonical designation or an orderable fact. It is clearly distinct from siblings like bom_extract (extraction) or catalog_check (catalog membership) because it is framed as a gate on purchased-line orderability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to run it ('before quoting or releasing a package') and why (sourcing work silently deferred per revision), and names the alternative input path — pass `rows` instead of `assembly` for BOM rows already in hand. It also states the negative case (a hand-modelled 'Bracket' is never flagged), which bounds the tool's reach.

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