Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

list_instances

Read-only

Lists running Autodesk Inventor instances with name, project, and open documents, and reports any manually opened instances the server cannot reach, even while busy.

Instructions

The Inventors this server is connected to — name, project, open documents — and any other running Inventor it can't reach (opened by hand). Answers even while they are busy.

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": "list_instances"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false. The description adds real value beyond them: it discloses that results cover both connected instances and ones 'it can't reach (opened by hand)', and that the call is non-blocking — 'Answers even while they are busy' — which is exactly the kind of liveness trait annotations cannot express. It stops short of saying anything about how stale or authoritative the open-documents data is.

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?

Two sentences, both load-bearing, with the connected/unreachable split front-loaded. The opening is a noun fragment ('The Inventors this server is connected to') rather than a clean clause, and the parenthetical '(opened by hand)' is doing work the main sentence could do better.

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 zero parameters, an output schema, and read-only annotations, the burden on the description is small and it meets it: what is listed, the two instance classes, and liveness are all covered. Only the absence of any routing guidance toward or away from sibling tools like connect keeps it out of the top band.

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?

The tool takes zero parameters and the input schema is empty, so there is nothing to disambiguate; a 4 is the baseline for a no-argument tool. The description also sketches the response fields, which is a bonus even though the output schema exists.

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 the resource precisely — the Inventor instances the server is connected to — and even enumerates the salient facts returned (name, project, open documents). It distinguishes two categories of instance (connected vs. running-but-unreachable), which is a genuinely specific scope, though the verb 'list' lives only in the tool name rather than the prose.

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?

Usage is implied rather than stated: it reads as a discovery call to make before acting on an Inventor session. There is no explicit 'use this when' or any named alternative among siblings (e.g. connect) telling the agent what to do with the results or when to skip it. The 'answers even while they are busy' clause hints at suitability for a pre-flight check, but the agent must infer it.

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