Skip to main content
Glama
fusion-cam

fusion-cam

status

Check whether the Fusion add-in is reachable and its main thread responsive, list open documents and active workspace/command, and report any crash from the last call.

Instructions

Check the Fusion connection: add-in reachable, Fusion's main thread responsive, open documents, active workspace/command, and whether Fusion crashed during a call last time (last_crash).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 burden, and "Check" does imply a non-mutating probe while the enumerated fields describe what is observed. The mention of last_crash usefully signals that crash state persists from a prior call, which is genuine behavioral context. However, it does not disclose whether the probe blocks on the main thread, how long it may take, or whether it is safe to call at any time — material facts for a health-check tool.

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?

A single sentence, front-loaded with the core action and then a tight comma-separated list of the checks performed. Every clause conveys distinct information and the last_crash parenthetical is inline rather than a separate trailing sentence.

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?

The tool is simple (no parameters) and an output schema exists, so return shape need not be explained; the description still enumerates the checked items so an agent knows what to look for. The remaining gap is procedural — when to reach for this versus reload_api or inspect, and what a failure outcome implies.

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, so the baseline is 4 and there is no parameter meaning left to add. The description does not waste words restating schema details, which is correct here.

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 specific verb ("Check") and a specific resource ("the Fusion connection") and then enumerates exactly what is inspected: add-in reachability, main-thread responsiveness, open documents, active workspace/command, and last_crash. That is far more informative than the bare name "status". It stops short of distinguishing this from sibling diagnostics such as cam_status or inspect, so it is clear but not sibling-differentiated.

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 only implied: the fact that it reports reachability and last_crash suggests it is a pre-flight/convalescence check before other calls, but the description never says "call this before invoking other tools" or names an alternative. No when-not conditions are given, and no guidance on how to react to a negative result (e.g., use reload_api).

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