Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

load_library

Loads a Python helper file into Inventor's execute_python namespace and keeps it available per project, avoiding repeated function definitions and reporting load time plus slowest lines.

Instructions

Run a Python file into this Inventor's execute_python namespace and keep it there: after reload_api, a new namespace or a new server it is loaded again by itself (remembered per project). For helper functions you would otherwise redefine every time. Says how long it took and which lines were slowest — a COM call at module level is the usual culprit. A file at ~/.inventor-mcp/startup.py (or INVENTOR_MCP_STARTUP) is loaded for every Inventor.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses persistence semantics (remembered per project, reloaded after reload_api, new namespace, or new server), timing feedback, and a global startup hook. It omits error behavior for a bad path and whether a re-load of the same path replaces or appends to the namespace.

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?

Front-loaded with the core action and persistence contract, then supporting detail about timing and startup. The pacing sentence ('Says how long it took…') is slightly conversational but still carries diagnostic information.

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?

Output schema exists, so return values need not be explained. For a stateful mutation with no annotations, the description covers persistence, lifecycle, and side effects well; only path validation and namespace-collision behavior are missing.

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

Parameters2/5

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

Schema coverage is only 50% and the undocumented parameter is the required one — 'path'. The description never says whether it must be absolute, must exist, or what happens on a bad path; it only incidentally mentions a startup file location. The optional `instance` parameter is documented in the schema, so the description adds nothing there.

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 ('Run a Python file into this Inventor's execute_python namespace') plus the key distinction that it persists, which separates it from execute_python and reload_api. An agent can identify the tool's job without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'For helper functions you would otherwise redefine every time' gives an explicit use case, and the reload_api/new-server survival notes clarify when persistence matters. It never explicitly names execute_python as the alternative for one-off code, so the exclusion side is only implied.

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