Skip to main content
Glama

Catalog Search

catalog_search
Read-only

Search a curated catalog of off-the-shelf screws, bearings, rings, and more to confirm which standard parts, sizes, and stocked lengths are actually available before committing design geometry.

Instructions

Browse the off-the-shelf catalog: which standard components actually EXIST, in which sizes, in which stocked lengths. Call it while designing, before you commit geometry to a number — it is the difference between a design somebody can build and one that needs a special.

The dimensional corpora (threads/bearings/stock) tell you what a part measures. This one tells you whether it is a thing you can buy. Nothing else in AnkusDrive knows that an ISO 4762 M4×12 is a stocked item and an M4×13 is not.

Every argument is an optional filter: family screw | set_screw | nut | washer | retaining_ring | pin | bearing | oring | threaded_rod standard a product standard or alias — "ISO 4762" or "DIN 912" kind the product's kind tag (socket_head_cap_screw, nyloc_nut, ...) size thread designation, nominal mm, shaft/bore mm, or AS568 dash length an exact stocked length, or a min_length/max_length window (mm) grade property class / material ("8.8", "A2-70", "NBR70") drive hex_socket | hex limit max rows (default 50)

Offline, deterministic, zero network.

Returns {ok, count, truncated, items, standards, fidelity, captured, market, not_covered}. Each item is {standard, name, family, kind, drive, size, size_kind, lengths (the stocked ladder, narrowed to any length filter), length_count, grades, length_measured, designation?}. Availability is a curated snapshot of a MARKET (see market and captured), not physics — and read not_covered before concluding from an empty result that a part does not exist.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
sizeNo
driveNo
gradeNo
limitNo
familyNo
lengthNo
standardNo
workspaceNoRun this call in this named workspace
max_lengthNo
min_lengthNo

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 only cover readOnlyHint and openWorldHint; the description adds the operational profile anyway ('offline, deterministic, zero network') and, with no output schema present, documents the full return shape and the meaning of truncated/standards/fidelity/captured/market/not_covered. Crucially it warns that availability is a curated market snapshot rather than physics and that an empty result must be read against not_covered before concluding a part doesn't exist — exactly the kind of false-negative trap an agent would otherwise fall into.

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?

Well front-loaded — purpose, then the contrast with dimensional corpora, then an indented argument block, then returns and caveats — so an agent can skim the top and stop. Slightly verbose in the framing ('the difference between a design somebody can build and one that needs a special') and the argument list is prose-indented rather than terse, costing a little density.

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?

Eleven all-optional filters, no output schema, and thin annotations — this is the hardest case for a description, and it covers argument semantics, return shape, determinism, and the semantic limits of the data. The only thing left implicit is whether multiple filters AND together, which is the expected default for a search tool.

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 9% (only `workspace` is described in-schema), so the description carries the burden — and it does, enumerating the family values, explaining that `standard` accepts aliases (DIN 912 ≡ ISO 4762), that `size` covers thread/nominal-mm/shaft-bore/AS568 dash, that `length` is either exact or a min_length/max_length window, plus grade, drive, and limit defaults. Only `workspace` is left to the schema, and the length-vs-min/max_length relationship is spelled out where the schema is silent.

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?

Specific verb+resource ('Browse the off-the-shelf catalog') plus explicit scope: existence of standard components, sizes, stocked lengths. It sharply differentiates itself from the dimensional corpora ('what a part measures') and from the rest of the suite ('whether it is a thing you can buy'), and the M4×12 vs M4×13 example makes the distinction concrete.

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 timing guidance: 'Call it while designing, before you commit geometry to a number,' which tells the agent when in a workflow this belongs. It contrasts with the dimensional corpora but never names the obvious sibling alternatives (catalog_nearest, catalog_check, catalog_check/designation_check) that an agent might otherwise confuse it with.

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