Skip to main content
Glama
Sign In
Fusion Native MCP

Fusion Native MCP

by Dawn-Of-Justice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fusion_edit_component_parameters

Edit model parameters for a selected component while rejecting stale state, foreign parameters, external links, and unacknowledged repeats. Recomputes feature errors and returns before/after definition states.

Instructions

Edit only the selected component's existing model parameters. Reject stale state, foreign parameters, external links and unacknowledged repeated instances. Recompute and check new feature errors; return before/after definition states.

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>",
      "operation_id": "<operation_id>",
      "spec": "<spec>"
    },
    "name": "fusion_edit_component_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
document_idYes
operation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Given that no annotations are provided, the description carries full responsibility for behavioral disclosure. It explicitly states rejection of stale state, foreign parameters, external links, and unacknowledged repeated instances, and mentions recomputation and error checks, plus returning before/after states. This is thorough for a mutation tool, though it does not cover authorization or rollback 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?

The description is concise, front-loading the purpose with 'Edit only the selected component's existing model parameters,' then adding constraints and consequences in a few sentences. Every sentence adds value and there is no redundant information.

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

Completeness3/5

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

The description covers behavioral aspects and return states, but omits parameter semantics and detailed return structure. Given the complexity of the nested spec and lack of output schema, more guidance on how to formulate the spec and what the before/after states look like would improve completeness. It is adequate but not complete.

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?

The description makes no reference to any of the input parameters, despite schema description coverage being 0%. It does not explain path, expected_component, expected_fingerprint, expressions, or allow_shared_definition_edit. The schema itself has descriptions, but the tool description fails to add meaning or tie them together, leaving the agent to rely on schema alone.

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 states the tool edits only the selected component's existing model parameters, using a specific verb and resource. It also distinguishes from siblings by emphasizing 'only' and 'existing', and lists rejection criteria, making the purpose 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 provides context on what the tool does but does not explicitly state when to use it versus alternatives like fusion_set_parameter. It implies that it is for editing component parameters with strict validation, but no direct comparison or exclusion is given.

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