Skip to main content
Glama
Sign In
kompas3d

kompas3d

by hymaxo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_model

Save a KOMPAS-3D model as editable native M3D or A3D file at a specified absolute path. Prevents accidental overwrites unless explicitly enabled.

Instructions

Save editable native M3D/A3D at an absolute path; no overwrite by default.

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": {
      "document_id": "<document_id>",
      "path": "<path>"
    },
    "name": "save_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
overwriteNo
document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description itself must carry behavioral detail. It discloses two useful traits: the output is an editable native M3D/A3D file and overwrite is off by default. It does not disclose what happens on collision without overwrite, whether directories are created, or any return/error behavior.

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?

One compact, front-loaded sentence that packs purpose, format, path constraint, and default overwrite behavior without filler.

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

Completeness3/5

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

For a three-parameter tool with no output schema and no annotations, the core is covered: what, where, format, overwrite default. Missing guidance on choosing this over export_model/save_document and collision/error behavior leaves some ambiguity, but the tool is simple enough that this is adequate.

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 description coverage is 0%, so the description must compensate. It clarifies path as absolute and overwrite as defaulting to false, adding real meaning beyond titles. However, document_id is left entirely to its schema title, and no parameter examples or value formats are provided.

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?

The description names a specific action (save), resource (editable native M3D/A3D model), and destination (absolute path), which is clear. It does not explicitly name a sibling to distinguish from, although 'editable native' implies contrast with export_model or save_document.

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 wording implies use this when an editable native-format save at an explicit filesystem path is needed. It gives no explicit when-to-use vs. alternatives, leaving the agent to infer the boundary against export_model and save_document.

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