Xem Studio: Part Dimensions & CAD

Browse and filter the catalog (lists of matching objects)

find_geometry

Read-onlyIdempotent

BROWSE: list many matching objects, filtered by keyword, category, group, kind or release year, with paging. Use it when the user wants options or a list ('which M3 screws are there', 'all NEMA motors', '2023 phones', 'free files in Fasteners'), or to find a slug when the name is vague. Not for one object's numbers: for a named object call get_part_dimensions_bolt_pattern_cad instead (one call returns its full sheet, fits and files). Returns summaries (overall size, file count, URL), with key dimensions inline for the top three. Matching: every query word must appear in the object's name, aliases, tags, category or group, case-insensitive ('80-40', '80 x 40' and '8040' alike); filters combine with AND. An empty result is not an error: retry with fewer words, or file request_object. Read-only against the published catalog snapshot; no auth, no charge.

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

Input Schema

Name	Required	Description
`kind`	No	modern/vintage: a product; standard: a part defined by a published standard; hardware: a generated part with free files.
`year`	No	Release year for products: '2023', '2020s' or '2010-2019'. Objects with no year are excluded when set.
`group`	No	Exact group name within the category, from list_categories.
`limit`	No	Page size; default 20.
`query`	No	Keywords; omit to list by filters alone.
`offset`	No	Start index; pass next_offset from the previous page.
`category`	No	Exact category name from list_categories.
`les_only`	No	Only parts used in Long Earth Society builds.
`free_only`	No	Only objects with free files.

Output Schema

Name	Required	Description
`next`	No	What to call next: get_geometry for a full sheet, or a hint when nothing matched.
`count`	No	Summaries in this page.
`total`	Yes	Objects matching, across all pages.
`offset`	No	Index of the first summary in this page.
`objects`	Yes	Summaries, best match first.
`next_offset`	No	Offset to pass for the next page, or null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 28, 2026

changedInput schema / properties / category / description

Previous value: -"Exact category name from list_categories, e.g. 'Hardware'."New value: +"Exact category name from list_categories."

changedInput schema / properties / free_only / description

Previous value: -"Only objects whose files are free to download."New value: +"Only objects with free files."

changedInput schema / properties / group / description

Previous value: -"Exact group name within a category from list_categories, e.g. 'Fasteners'."New value: +"Exact group name within the category, from list_categories."

changedInput schema / properties / kind / description

Previous value: -"modern/vintage = a product; standard = a part defined by a standard; hardware = a generated part with free files."New value: +"modern/vintage: a product; standard: a part defined by a published standard; hardware: a generated part with free files."

changedInput schema / properties / limit / description

Previous value: -"Page size, default 20."New value: +"Page size; default 20."

changedInput schema / properties / query / description

Previous value: -"Keywords, e.g. 'M3 heat set insert', 'tri clamp ferrule 2in', 'raspberry pi 5'. Omit to list by filters alone."New value: +"Keywords; omit to list by filters alone."

changedInput schema / properties / year / description

Previous value: -"Release year for products: '2023', '2020s' or '2010-2019'; objects without a year are then excluded."New value: +"Release year for products: '2023', '2020s' or '2010-2019'. Objects with no year are excluded when set."

addedOutput schema / properties / count / description
```
Added value: +"Summaries in this page."
```

addedOutput schema / properties / next / description

Added value: +"What to call next: get_geometry for a full sheet, or a hint when nothing matched."

addedOutput schema / properties / next_offset / description

Added value: +"Offset to pass for the next page, or null on the last page."

addedOutput schema / properties / objects / description
```
Added value: +"Summaries, best match first."
```
addedOutput schema / properties / objects / items / properties / category / description
```
Added value: +"Category, e.g. 'Hardware'."
```

addedOutput schema / properties / objects / items / properties / free_files / description

Added value: +"How many free STEP/STL files the object has (0 = dimension sheet only)."

addedOutput schema / properties / objects / items / properties / group / description
```
Added value: +"Group within the category, e.g. 'Fasteners'."
```
addedOutput schema / properties / objects / items / properties / kind / description
```
Added value: +"modern | vintage | standard | hardware."
```
addedOutput schema / properties / objects / items / properties / name / description
```
Added value: +"Display name."
```
addedOutput schema / properties / objects / items / properties / overall_mm / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / objects / items / properties / overall_mm / description

Added value: +"Overall size in mm: length, width, height (diameter for round parts); null where unpublished."

addedOutput schema / properties / objects / items / properties / slug / description

Added value: +"Object slug: pass it to get_geometry, get_fits, get_free_files or get_file_content."

addedOutput schema / properties / objects / items / properties / url / description
```
Added value: +"The object's page on xemstudio.com."
```

addedOutput schema / properties / offset / description

Added value: +"Index of the first summary in this page."

addedOutput schema / properties / total / description

Added value: +"Objects matching, across all pages."

Changed3 schema fields changedOct 24, 2026

changedInput schema / properties / kind / description

Previous value: -"modern/vintage = a product; standard = a part defined by a standard; hardware = a generated part with free files; list = a complete assembly with its parts list."New value: +"modern/vintage = a product; standard = a part defined by a standard; hardware = a generated part with free files."

changedInput schema / properties / kind / enum

Previous value: -[
-  "modern",
-  "vintage",
-  "standard",
-  "hardware",
-  "list"
-]New value: +[
+  "modern",
+  "vintage",
+  "standard",
+  "hardware"
+]

changedInput schema / properties / les_only / description

Previous value: -"Only parts used in Long Earth Society engine builds."New value: +"Only parts used in Long Earth Society builds."

Changed10 schema fields changedOct 22, 2026

changedInput schema / properties / category / description

Previous value: -"Exact top-level category: 'Stirling engines', 'Hardware', 'Electronics', 'Power & cooling', 'Vintage forms', 'Everyday mounts'. list_categories gives the current list."New value: +"Exact category name from list_categories, e.g. 'Hardware'."

changedInput schema / properties / free_only / description

Previous value: -"true = only objects with free files (generated STEP/STL) or a free official CAD source."New value: +"Only objects whose files are free to download."

changedInput schema / properties / group / description

Previous value: -"Exact group within a category, e.g. 'Fasteners', 'Framing', 'Sanitary clamp fittings', 'Single-board computers'. list_categories gives every group with counts."New value: +"Exact group name within a category from list_categories, e.g. 'Fasteners'."

changedInput schema / properties / kind / description

Previous value: -"modern = a current product (phone, board); vintage = an older product; standard = a part defined by a standard (bearing, screw size); hardware = a generated part with free files; list = a complete engine build list."New value: +"modern/vintage = a product; standard = a part defined by a standard; hardware = a generated part with free files; list = a complete assembly with its parts list."

changedInput schema / properties / les_only / description

Previous value: -"true = only parts used in Long Earth Society engine builds."New value: +"Only parts used in Long Earth Society engine builds."

changedInput schema / properties / limit / description

Previous value: -"Results per page, default 20."New value: +"Page size, default 20."

changedInput schema / properties / offset / description

Previous value: -"Skip this many results (from next_offset), default 0."New value: +"Start index; pass next_offset from the previous page."

changedInput schema / properties / query / description

Previous value: -"Words that must all appear, e.g. 'M3 heat set insert', 'tri clamp ferrule 2in', '4080 extrusion', 'raspberry pi 5'. Omit to list by filters only."New value: +"Keywords, e.g. 'M3 heat set insert', 'tri clamp ferrule 2in', 'raspberry pi 5'. Omit to list by filters alone."

changedInput schema / properties / year / description

Previous value: -"Release year filter for modern and vintage products: '2023', '2020s' or '2010-2019'. Objects without a year are excluded when set."New value: +"Release year for products: '2023', '2020s' or '2010-2019'; objects without a year are then excluded."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "next": {
+      "type": "string"
+    },
+    "next_offset": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "objects": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "free_files": {
+            "type": "integer"
+          },
+          "group": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "overall_mm": {
+            "type": "object"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "objects"
+  ],
+  "type": "object"
+}

Changed10 schema fields changedOct 22, 2026

changedInput schema / properties / category / description

Previous value: -"Stirling engines | Hardware | Electronics | Power & cooling | Vintage forms"New value: +"Exact top-level category: 'Stirling engines', 'Hardware', 'Electronics', 'Power & cooling', 'Vintage forms', 'Everyday mounts'. list_categories gives the current list."

addedInput schema / properties / free_only / description

Added value: +"true = only objects with free files (generated STEP/STL) or a free official CAD source."

changedInput schema / properties / group / description

Previous value: -"e.g. Fasteners, Tri-clamp, Single-board computers, Batteries"New value: +"Exact group within a category, e.g. 'Fasteners', 'Framing', 'Sanitary clamp fittings', 'Single-board computers'. list_categories gives every group with counts."

addedInput schema / properties / kind / description

Added value: +"modern = a current product (phone, board); vintage = an older product; standard = a part defined by a standard (bearing, screw size); hardware = a generated part with free files; list = a complete engine build list."

changedInput schema / properties / kind / enum

Previous value: -[
-  "modern",
-  "vintage",
-  "standard",
-  "hardware"
-]New value: +[
+  "modern",
+  "vintage",
+  "standard",
+  "hardware",
+  "list"
+]

changedInput schema / properties / les_only / description

Previous value: -"Only parts used in Long Earth Society Stirling/thermoacoustic engine builds"New value: +"true = only parts used in Long Earth Society engine builds."

addedInput schema / properties / limit

Added value: +{
+  "description": "Results per page, default 20.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many results (from next_offset), default 0.",
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / query / description

Previous value: -"Free text: name, alias, tag, e.g. 'M3 heat set insert', 'tri clamp ferrule', 'raspberry pi 5'"New value: +"Words that must all appear, e.g. 'M3 heat set insert', 'tri clamp ferrule 2in', '4080 extrusion', 'raspberry pi 5'. Omit to list by filters only."

changedInput schema / properties / year / description

Previous value: -"2023, 2020s, or 2010-2019 (electronics and vintage only)"New value: +"Release year filter for modern and vintage products: '2023', '2020s' or '2010-2019'. Objects without a year are excluded when set."

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world safety, and the description adds genuinely new operational detail: the AND-combination of query words and filters, case-insensitive matching across name/aliases/tags, that an empty result is not an error and how to recover, and that calls are free with no auth. It partially previews the return payload (summaries with overall size, file count, URL, inline dimensions for the top three), though it doesn't fully specify pagination metadata semantics beyond referring to next_offset in the schema.

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?

It is front-loaded with a bracketed mode label and the core action before alternatives and matching rules, and every sentence carries usable information. It is on the dense/long side for a browse tool, but nothing is padding.

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 an output schema present, the description correctly avoids restating return structure in full while still signaling summary-level results, and it covers matching rules, empty-result recovery, safety/cost, and the sibling routing decision. An agent has everything needed to choose and invoke it correctly.

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 100%, so the baseline is 3; the description still adds value by explaining that query words are ANDed and matched case-insensitively against name, aliases, tags, category or group, including the "80-40"/"80 x 40"/"8040" equivalence rule. The filter semantics are thereby explained at a level the per-field schema descriptions don't reach.

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 opens with an explicit verb+resource ("BROWSE: list many matching objects") and enumerates the filter axes (keyword, category, group, kind, release year, paging). It clearly distinguishes itself from the sibling that returns a single object's data by naming get_part_dimensions_bolt_pattern_cad as the alternative.

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?

It gives concrete when-to-use triggers with quoted user phrasings ("which M3 screws are there", "2023 phones"), states the secondary use (finding a slug when the name is vague), and gives an explicit when-not with the sibling to use instead. No inference is required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Xem Studio: Part Dimensions & CAD tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?