Skip to main content
Glama

Xem Studio: Part Dimensions & CAD

Read one object's mating features

get_fits
Read-onlyIdempotent

For designing a part that bolts to, clamps, slides over, presses into or otherwise mates with a real object (bracket holes, bore clearance, boss pocket, shaft fit). Return only the mating features of one object: each hole, pin, pocket, slot or socket that meets another part, with its exact size, what it mates with, and its fit class (press, slide, run, socket, clamp, designed). Use it before designing or printing a part that must fit this object, or when get_geometry's full sheet is more than needed; the same features also come with get_free_files. Every size is exact with no clearance: add your process allowance to press, slide, run and socket features; designed and clamp features are already the final gap and stay as drawn. An object with no mating features returns an empty list, not an error. Read-only, no auth.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "object": "<object>"
    },
    "name": "get_fits"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYesObject slug as returned by find_geometry or find_by_dimensions, e.g. '4080-aluminum-extrusion'. An exact object name or alias also resolves; anything else is an error with a hint to search first.

Output Schema

NameRequiredDescriptionDefault
noteNoGuidance for the empty case.
matingYesMating features; empty when none are recorded.
objectYesObject slug.
dimensionsNoHow to read the sizes.
fit_classesNoDefinition of each fit class and what allowance, if any, to add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / object / description
      Previous value: -"Slug as returned by find_geometry or find_by_dimensions, e.g. '4080-aluminum-extrusion'. An exact name or alias also resolves."New value: +"Object slug as returned by find_geometry or find_by_dimensions, e.g. '4080-aluminum-extrusion'. An exact object name or alias also resolves; anything else is an error with a hint to search first."
    • addedOutput schema / properties / dimensions / description
      Added value: +"How to read the sizes."
    • addedOutput schema / properties / fit_classes / additionalProperties
      Added value: +true
    • addedOutput schema / properties / fit_classes / description
      Added value: +"Definition of each fit class and what allowance, if any, to add."
    • addedOutput schema / properties / mating / description
      Added value: +"Mating features; empty when none are recorded."
    • addedOutput schema / properties / mating / items / properties / exact / description
      Added value: +"Its exact size, in mm, with no clearance."
    • addedOutput schema / properties / mating / items / properties / feature / description
      Added value: +"The feature, e.g. 'M3 mounting holes (4)'."
    • addedOutput schema / properties / mating / items / properties / files
      Added value: +{
      +  "description": "Which of the object's files carry this feature ('all' or a file name).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / mating / items / properties / fit / description
      Added value: +"Fit class: press | slide | run | socket | clamp | designed."
    • addedOutput schema / properties / mating / items / properties / mates / description
      Added value: +"What it meets: another object, a standard part, or a fastener size."
    • changedOutput schema / properties / mating / items / required
      Previous value: -[]New value: +[
      +  "feature",
      +  "exact",
      +  "fit"
      +]
    • addedOutput schema / properties / note / description
      Added value: +"Guidance for the empty case."
    • addedOutput schema / properties / object / description
      Added value: +"Object slug."
  2. Changed2 schema fields changed
    • changedInput schema / properties / object / description
      Previous value: -"The object's slug exactly as find_geometry or find_by_dimensions returns it (e.g. '4080-aluminum-extrusion'). A name or alias also works; slugs are safest."New value: +"Slug as returned by find_geometry or find_by_dimensions, e.g. '4080-aluminum-extrusion'. An exact name or alias also resolves."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "dimensions": {
      +      "type": "string"
      +    },
      +    "fit_classes": {
      +      "type": "object"
      +    },
      +    "mating": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "exact": {
      +            "type": "string"
      +          },
      +          "feature": {
      +            "type": "string"
      +          },
      +          "fit": {
      +            "type": "string"
      +          },
      +          "mates": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "object": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "object",
      +    "mating"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / object / description
      Previous value: -"Slug, e.g. 'tri-clamp-power-pistons'"New value: +"The object's slug exactly as find_geometry or find_by_dimensions returns it (e.g. '4080-aluminum-extrusion'). A name or alias also works; slugs are safest."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world. The description adds crucial domain behavior beyond that: sizes are exact with no clearance, process allowance must be added to press/slide/run/socket features, designed/clamp features are already final gaps, and an empty list rather than an error is returned when no mating features exist.

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?

Dense but mostly front-loaded: purpose and use case come early, then exactness rules and edge-case behavior. There is mild repetition between the opening 'For designing a part that bolts to...' framing and the later 'Use it before designing or printing a part...' sentence, which costs a point.

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?

An output schema exists, so return structure need not be explained; the description instead covers the semantics an agent needs—fit classes, allowance rules, and empty-list behavior. Nothing required for correct invocation is missing.

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

Parameters3/5

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

Schema coverage is 100% and the object parameter is fully documented in the schema, including slug resolution and error behavior. The description adds only the scoping phrase 'one object' and does not elaborate on the parameter beyond the schema, so baseline 3 is appropriate.

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 and resource: 'Return only the mating features of one object: each hole, pin, pocket, slot or socket that meets another part, with its exact size, what it mates with, and its fit class.' It also differentiates from siblings by contrasting with get_geometry's full sheet and noting get_free_files also includes these features.

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?

Gives explicit when-to-use ('before designing or printing a part that must fit this object') and names the alternative ('when get_geometry's full sheet is more than needed'), plus notes get_free_files overlaps. An agent can select this tool without opening another schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources