Skip to main content
Glama

cad_read

Read-only

Use a read-only script to inspect an open CAD, BIM, or 3D model and return results without modifying it.

Instructions

Run a script that only INSPECTS the app's open model. Nothing may be changed.

app: an id from cad_apps, for example "blender", "autocad", "revit". code: the script, in the language given by cad_skill(app). Set result = ... (or end with an expression) to return data; printed text comes back too. instance: port of one instance when cad_apps lists several of the same app.

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": {
      "app": "<app>",
      "code": "<code>"
    },
    "name": "cad_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
codeYes
instanceNo
timeout_sNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces and sharpens this by stressing nothing may be changed, and adds behavior the annotations do not cover: how data is returned (assign to `result` or end with an expression) and that printed text is also returned.

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 critical constraint is front-loaded in the first sentence, followed by three tight per-parameter lines with no filler; the line-broken layout makes each parameter's meaning scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value explanation is not required, and the description instead covers the script-language source and cross-tool id references. The gaps are timeout_s behavior and what happens on script errors or timeouts, which matter for a 120-second default execution tool.

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 description coverage is 0%, so the description must carry the load and largely does: app is tied to ids from cad_apps with concrete examples, code's language is tied to cad_skill and its return convention explained, and instance is defined as a port when several instances exist. Only timeout_s is left undocumented beyond its schema default.

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?

Names a specific verb and resource: run a script that only INSPECTS the app's open model. The emphatic 'Nothing may be changed' makes the read-only scope unmistakable and effectively separates it from a modify-style sibling, though no sibling is named outright.

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?

The read-only constraint implies that any change must go elsewhere, and cad_skill is referenced for determining the script language, but there is no explicit 'use X instead when you need to modify' statement or prerequisite guidance.

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