Skip to main content
Glama
Sign In
Fusion Native MCP

Fusion Native MCP

by Dawn-Of-Justice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_cam_tools

Read CAM tool definitions with fingerprints to detect changes between selection and use, ensuring the correct tools are applied in Autodesk Fusion.

Instructions

Read tool definitions with fingerprints to detect changes between selection and use.

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>",
      "library_url": "<library_url>"
    },
    "name": "fusion_cam_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
document_idYes
library_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses a read action and the fingerprint-based change detection, which suggests a non-mutating inspection tool. It does not explain how fingerprints work, what triggers a change warning, or what happens when a change is detected, leaving some behavior unexplained.

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?

The description is a single concise sentence with no filler. It is front-loaded with the main verb and resource, but the cryptic 'fingerprints' term could be explained more for the same word count.

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

Completeness2/5

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

Given four parameters, no output schema, and no annotations, this description is too minimal for an agent to invoke the tool confidently. It omits parameter semantics, result shape, and practical workflow details, so it only partially covers the context needed for correct use.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to any of the four parameters. It does not mention document_id, library_url, limit, or offset, so an agent cannot determine how to populate these parameters from the description alone.

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 clearly states the tool reads tool definitions and uses fingerprints to detect changes between selection and use. It names a specific resource and purpose, which is enough to distinguish it from inventory, browsing, and other CAM utility tools, though it does not explicitly compare itself with any sibling.

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 phrase 'between selection and use' implies the intended moment to call this tool and hints at a workflow purpose. However, it does not explicitly state when not to use it or point to alternatives, so the guidance remains inferred rather than fully explicit.

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