Skip to main content
Glama
fusion-cam

fusion-cam

reload_api

Re-imports edited ops modules from disk and clears the execute_python namespace so Python changes take effect without restarting Fusion.

Instructions

Re-import the add-in's ops modules from disk (after editing addin/FusionMCP/ops/.py) and clear the execute_python namespace. Changes to FusionMCP.py or bridge/ need the add-in stopped and run again in Fusion (Shift+S > Add-Ins).

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full burden and does meaningful work: it discloses a destructive side effect (the execute_python namespace is cleared) and a hard limitation (this reload does not pick up FusionMCP.py or bridge/* changes). It does not say what happens if a module fails to import, and relies on the output schema for return details.

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?

Two sentences, both front-loaded and earning their place: the first states the action and its file scope, the second states the limitation with the exact workaround. No filler or repetition of the name.

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?

For a zero-param tool with an output schema, this covers what it does, when to invoke it, its main side effect, and its scope limit. Only failure behavior (broken modules, partial reload) is left unspecified, which is a minor gap.

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?

There are zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies the tool takes no arguments.

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 gives a precise verb and resource: 'Re-import the add-in's ops modules from disk', scoped explicitly to addin/FusionMCP/ops/*.py. It also names the second effect (clearing the execute_python namespace), which ties it to a concrete sibling tool. It stops short of a full one-line statement of purpose but an agent can tell exactly what it does.

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?

The trigger is explicit: use it after editing addin/FusionMCP/ops/*.py. It also gives a clear exclusion — changes to FusionMCP.py or bridge/* require stopping the add-in and restarting (Shift+S > Add-Ins) rather than calling this tool. It lacks an explicit named alternative tool, but the when/when-not boundary is clear.

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