Skip to main content
Glama
Sign In
Fusion Native MCP

Fusion Native MCP

by Dawn-Of-Justice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_api_docs

Search Fusion API documentation using regular expressions to locate classes, members, or descriptions, optionally filtered by namespace.

Instructions

Search the installed Fusion API docs by regular expression, including adsk.cam.

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": {
      "search_pattern": "<search_pattern>"
    },
    "name": "fusion_api_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoall
search_patternYes
namespace_filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.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 carries the full behavioral burden. It communicates that the search is regex-based, scoped to installed docs, and includes adsk.cam, which is useful. However, it does not state return format, whether output is just matches or full descriptions, or how broad the search is.

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?

The description is a single, front-loaded sentence with no waste. It states the operation, the mechanism, and the important scope qualifier compactly.

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?

The tool has three parameters, no parameter schema descriptions, no annotations, and no output schema. The description is too minimal to fully guide correct invocation; it lacks the meaning of category, the role of namespace_filter, and what the returned results contain.

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 description coverage is 0%, so the description must compensate, but it only implicitly covers search_pattern via 'regular expression' and namespace_filter via 'including adsk.cam'. The category parameter is completely unmentioned, and no parameter is explicitly explained or mapped to the schema.

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?

The description clearly identifies a specific action ('Search'), a concrete resource ('installed Fusion API docs'), and a distinguishing mechanism ('by regular expression, including adsk.cam'). This clearly differentiates it from all sibling tools, none of which are documentation-search tools.

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 description implies when to use it: whenever an agent needs to search the installed Fusion API documentation. However, it provides no explicit conditions, exclusions, or comparisons to alternatives, so some inference is required.

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