Skip to main content
Glama
Sign In
Fusion Native MCP

Fusion Native MCP

by Dawn-Of-Justice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_activate_document

Switch to a specific open document by its creation ID, rejecting duplicate selections and preserving other open files.

Instructions

Activate exactly one already-open document by creation ID. Reject duplicate IDs; never save or close other documents.

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": {
      "current_document_id": "<current_document_id>",
      "target_document_id": "<target_document_id>",
      "operation_id": "<operation_id>"
    },
    "name": "fusion_activate_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYes
target_document_idYes
current_document_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden. It explicitly reveals important safety behaviors: it rejects duplicate IDs and never saves or closes other documents. It does not fully describe response format or error behavior, but the main side-effect boundaries are clearly stated.

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 two dense sentences with no filler. The core action is front-loaded, and the constrained behaviors are stated efficiently. Every clause earns its place.

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 no annotations, no output schema, and three required parameters, the description leaves significant gaps. It does not explain what the response looks like, how operation_id is used, or what happens to the currently active document. An agent would still need to guess about key invocation details.

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%, and the description does not compensate for any of the three required parameters. It mentions 'by creation ID' but never maps that to target_document_id, and it does not explain current_document_id or operation_id. The parameter names are somewhat self-explanatory, but the description adds little semantic value.

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 uses a specific verb and resource: 'Activate exactly one already-open document by creation ID.' It also clarifies scope and constraints ('exactly one', 'already-open'), which distinguishes it from tools like fusion_open_archive or fusion_documents. Even without naming a sibling, the action is unambiguous.

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 the tool: when the target document is already open and needs to be activated. However, it does not explicitly state when not to use it or mention alternatives such as fusion_open_archive or fusion_documents. Usage context is present but left to inference.

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