Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

reload_api

Hot-reload the wrapper (inventor_api.py and its api_*.py parts) from disk. Use after editing it — no Claude Code restart needed. Keeps the COM connections; clears this Inventor's execute_python namespace.

Instructions

Hot-reload the wrapper (inventor_api.py and its api_*.py parts) from disk. Use after editing it — no Claude Code restart needed. Keeps the COM connections; clears this Inventor's execute_python namespace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reload_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/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 so well: it discloses that COM connections survive while the execute_python namespace is cleared — i.e. what state is destroyed. It omits what happens on a failed reload (e.g. syntax error in the edited file), which is the main remaining risk an agent would want to know.

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?

Three short sentences, front-loaded with the action, then the trigger, then the side effects. No filler or repetition.

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?

An output schema exists, so return values need not be explained, and the side effects of the operation are stated. The only meaningful gap is failure behavior when the reloaded file is broken, which for a hot-reload tool an agent would benefit from knowing.

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 single 'instance' parameter is already fully documented in the schema, including the 'leave empty when only one is connected' rule. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

Names a specific verb ('Hot-reload') and an exact resource ('the wrapper — inventor_api.py and its api_*.py parts'), and clarifies the scope as 'this Inventor's' namespace, which separates it from execute_python and the modeling siblings.

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?

Gives a clear trigger condition: 'Use after editing it — no Claude Code restart needed.' It does not name an alternative tool or state when not to use it, but for a maintenance tool the trigger is unambiguous.

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