Skip to main content
Glama
hellstein-dev

fusion-mcp

timeline_edit_revolve

Change an existing revolve feature's angle and optional second angle by degrees or Fusion expression, with automatic revert if it errors.

Instructions

Change an existing revolve's angle (degrees; angle extents only) and angle_two (two-sided revolves).

Example: timeline_edit_revolve(feature=, angle=180).

Returns {"feature": item, "changed": [{"key", "parameter", "old_expression", "new_expression", "value", "value_unit"}]} (values in mm / deg). All given keys are applied together; if the feature (or any other) falls into the error state everything is reverted and the call fails with FUSION_API_ERROR, details.reverted = true — unless allow_errors=true. A key that does not apply to this feature fails with INVALID_PARAMS and details.available_keys; no key at all fails with 'nothing to change'.

Input Schema

NameRequiredDescriptionDefault
angleNoNumber in degrees, or a Fusion expression ('15 deg', 'a / 2')
featureYesFeature ref from timeline_list (or 'timeline:<name>')
angle_twoNoNumber in degrees, or a Fusion expression ('15 deg', 'a / 2')
allow_errorsNoKeep the change even if a feature falls into the error state (default: revert and fail)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully carries the behavioral burden: it explains atomic application of keys, revert-on-error behavior, FUSION_API_ERROR with details.reverted, INVALID_PARAMS with available_keys, and the effect of allow_errors=true. That is unusually complete for a mutation 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?

The sentence order is front-loaded: purpose, example, return shape, then error/revert semantics. Despite covering a nontrivial mutation, every sentence adds information needed to call or interpret the tool.

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

Completeness5/5

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

There is no output schema and no annotations, but the description supplies the return shape, error cases, revert behavior, and the allow_errors escape hatch. Together with the 100%-covered input schema, an agent has enough to invoke and interpret this tool correctly.

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?

Schema coverage is 100%, so the schema already documents all four parameters thoroughly. The description still adds useful meaning by clarifying that angle is limited to angle extents and angle_two applies only to two-sided revolves.

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 states a specific verb and resource: changing an existing revolve's angle and angle_two. The phrase 'angle extents only' and the angle_two restriction to two-sided revolves make the scope precise enough to distinguish it from create or generic parameter tools.

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?

It clearly indicates the context: editing an existing revolve's angle, with an example invocation. It also implicitly excludes non-angle edits via 'angle extents only' and limits angle_two to two-sided revolves, though it does not explicitly name sibling alternatives such as timeline_feature_parameters.

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