Skip to main content
Glama

Catalog Check

catalog_check
Read-only

Check whether a specific part designation (e.g., ISO 4762 M4×12 A2 or 608-2RS) is stocked, size-available, grade-listed, or catalogued, and get nearest length options and clear reason codes.

Instructions

Is this exact part something you can buy off the shelf?

Pass a canonical designation ("ISO 4762 M4×12 A2", "608-2RS") or the handle of a part whose designation was stamped when it was generated. Offline and deterministic.

Returns {ok, code, standard, size, length, stocked, grade_ok, reason, nearest, lengths, grades, fidelity, captured, market}, where code is: stocked the size/length exists and the material is listed (for a cut-to-length product like threaded rod, any length up to the longest stock bar counts, with a note that it is a cut) not_stocked the size exists but the LENGTH is not a stocked rung — nearest names the rungs either side size_not_stocked the standard does not cover this size at all grade_not_listed the size exists, that material does not not_catalogued the product standard is outside this corpus's coverage. That is an absence of evidence, explicitly NOT a claim that the part is unavailable — check not_covered from catalog_search undesignated there was no designation to check ok is True only for stocked.

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

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it is offline and deterministic, and it documents the meaning of every return code, including the important distinction between not_catalogued and unavailable. It also clarifies that ok is true only for stocked, which is essential for correct interpretation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose question, followed by input guidance and then structured return-code semantics. The length is justified because there is no output schema and the return codes are necessary for correct interpretation.

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?

Given that there is no output schema, the description carries the return-value burden well by defining the result object and every code value. It also explains the critical not_catalogued caveat and the absence-of-evidence semantics, leaving only minor parameter-precedence details unstated.

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?

With only 33% schema description coverage, the description compensates well for the two main parameters by explaining canonical designation syntax and the origin of a usable handle. It does not clarify precedence or whether designation and handle may both be supplied, and workspace is left to the schema.

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 states a specific question and resource: checking whether an exact part is buyable off the shelf from a canonical designation or handle. It distinguishes itself from catalog_search in one return-code note, but does not clearly differentiate from similar siblings such as designation_check or catalog_nearest.

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

Usage Guidelines3/5

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

It gives implied usage by saying to pass a canonical designation or stamped handle, but does not explicitly state when to use this tool instead of designation_check, catalog_nearest, or catalog_search. The guidance is adequate but leaves alternative selection largely to inference.

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