Xem Studio: Part Dimensions & CAD

Read one CAD file's contents

get_file_content

Read-onlyIdempotent

Return the contents of one free file so the geometry can be read or modified directly: STEP and DXF as UTF-8 text, STL as base64. Units are millimetres, true size. Use it after get_free_files gives the file name and the content itself is needed; use get_free_files when a download URL is enough, which is cheaper for large files. Files over 600 KB are not inlined: the response carries inlined=false, size_bytes and the URL to fetch instead. An unknown file name is an error that lists the valid names. Read-only, no auth, no charge.

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>",
      "file": "<file>"
    },
    "name": "get_file_content"
  }
}

Input Schema

Name	Required	Description
`file`	Yes	A file name exactly as get_free_files lists it, e.g. '4080-100'.
`format`	No	Default step. DXF exists only for 2D sections such as extrusion profiles.
`object`	Yes	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.

Output Schema

Name	Required	Description
`url`	Yes	Direct download URL for the same file.
`file`	Yes	File name.
`units`	No	mm.
`format`	Yes	step \| dxf \| stl.
`object`	Yes	Object slug.
`content`	No	The file contents, present when inlined is true.
`inlined`	No	False when the file was too large to include; fetch url instead.
`license`	No	License and credit.
`encoding`	No	utf-8 for STEP and DXF, base64 for STL.
`size_bytes`	No	File size.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 28, 2026

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 / content / description

Added value: +"The file contents, present when inlined is true."

addedOutput schema / properties / encoding / description

Added value: +"utf-8 for STEP and DXF, base64 for STL."

addedOutput schema / properties / file / description
```
Added value: +"File name."
```
addedOutput schema / properties / format / description
```
Added value: +"step | dxf | stl."
```

addedOutput schema / properties / inlined / description

Added value: +"False when the file was too large to include; fetch url instead."

addedOutput schema / properties / license / description
```
Added value: +"License and credit."
```
addedOutput schema / properties / object / description
```
Added value: +"Object slug."
```
addedOutput schema / properties / size_bytes / description
```
Added value: +"File size."
```
addedOutput schema / properties / units / description
```
Added value: +"mm."
```

addedOutput schema / properties / url / description

Added value: +"Direct download URL for the same file."

Changed4 schema fields changedOct 22, 2026

changedInput schema / properties / file / description

Previous value: -"File name from get_free_files, e.g. '4080-100' or 'spool-2in-6in'."New value: +"A file name exactly as get_free_files lists it, e.g. '4080-100'."

changedInput schema / properties / format / description

Previous value: -"Default step."New value: +"Default step. DXF exists only for 2D sections such as extrusion profiles."

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": {
+    "content": {
+      "type": "string"
+    },
+    "encoding": {
+      "type": "string"
+    },
+    "file": {
+      "type": "string"
+    },
+    "format": {
+      "type": "string"
+    },
+    "inlined": {
+      "type": "boolean"
+    },
+    "license": {
+      "type": "string"
+    },
+    "object": {
+      "type": "string"
+    },
+    "size_bytes": {
+      "type": "integer"
+    },
+    "units": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "object",
+    "file",
+    "format",
+    "url"
+  ],
+  "type": "object"
+}

AddedOct 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent, so the safety bar is low, yet the description adds real behavior: the 600 KB inlining cutoff with inlined=false/size_bytes/URL fallback, format-specific encodings, and that an unknown file name errors with the valid name list. No auth/no charge is extra context beyond annotations.

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?

Four dense sentences, front-loaded with the core action and formats before the alternative-routing note. Slightly redundant at the tail, where 'Read-only, no auth, no charge' overlaps what the annotations already declare, but nothing is bloated.

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?

For a 3-parameter read tool with an output schema and full annotation coverage, this is complete: it explains format encodings, the large-file fallback shape, and the error path for bad names. An agent has everything needed to call it and interpret the response.

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 adds meaning the schema lacks — units are millimetres at true size, and STEP/DXF are UTF-8 text versus STL base64. The 'after get_free_files gives the file name' note also clarifies how to populate the file parameter.

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 the contents of one free file') and immediately defines the scope: formats and encodings, units in millimetres. An agent can distinguish it from get_free_files because the description says content is inlined, not just a listing.

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?

Explicit sequencing: 'Use it after get_free_files gives the file name' and a clear alternative rule — use get_free_files when a download URL is enough, which is cheaper for large files. Both the when and the when-not are named with a sibling.

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?