Skip to main content
Glama
Sign In
fusion-mcp

fusion-mcp

by hellstein-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

timeline_rename

Renames features, sketches, construction elements, or timeline groups while keeping entity references valid; group refs update to timeline:.

Instructions

Rename a feature, sketch, construction element or timeline group. Entity refs stay valid; a group's ref becomes 'timeline:'. Bodies are renamed with the body_* tools, not here.

Returns {"item": item, "marker_position", "count"}.

Example: timeline_rename(item=, name="Base").

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": {
      "item": "<item>",
      "name": "<name>"
    },
    "name": "timeline_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesTimeline item: the 'ref' of a feature/sketch/construction element from timeline_list, or 'timeline:<name>' (groups)
nameYesNew name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the load, and it does disclose the key non-obvious side effect: entity refs stay valid but a group's ref mutates to 'timeline:<new name>'. It also pre-empts the missing output schema by spelling out the return shape. It does not mention permissions, duplicate-name behavior, or error cases for an invalid item ref.

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 rename scope comes first, then the behavioral consequence, then the exclusion, then the return shape and example — a well front-loaded order. Mentioning the excluded bodies case early prevents a wrong call before the agent reads further, and nothing is padding.

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?

With only two required params, no annotations and no output schema, the description covers the crucial ground: what can be renamed, ref stability, return shape and the sibling to avoid. Gaps remain around failure modes and whether renaming a group affects member refs, which matter for a mutation tool with no annotations.

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 both parameters are already documented and baseline would be 3. The description adds value beyond the schema by giving a concrete worked example (item=<extrude ref>, name="Base") and by reinforcing that group items are addressed as 'timeline:<name>', which clarifies how item is actually formed in practice.

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?

States a specific verb (Rename) and enumerates the exact resource classes it covers: feature, sketch, construction element, timeline group. It also draws a boundary against the nearest confusable sibling, body_rename, by saying bodies are renamed with the body_* tools, not here.

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?

Explicitly tells the agent when NOT to use it (bodies → body_* tools) and what the item argument should reference. It stops short of stating prerequisites, such as the fact that the ref must first come from timeline_list, and gives no guidance for the other rename-adjacent siblings like assembly_rename_component or timeline_edit_* beyond the body exclusion.

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