Skip to main content
Glama
Sign In
Fusion360 Live MCP

Fusion360 Live MCP

by tbrito88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Suppress Feature

suppress_feature

Disable one or more timeline features in a single batch to avoid multiple recomputes. Suppressing a Combine cut/join brings back its tool body, listing bodies_appeared to identify the source feature.

Instructions

Suppress (disable) one or more timeline features. Pass feature_names for a batch: it recomputes the timeline ONCE (one call per feature costs a full recompute each — ~2.5 s apiece on a 200+ item timeline). Suppressing a Combine cut/join brings its tool body back; the result lists bodies_appeared so you can suppress the feature that made it.

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

Input Schema

NameRequiredDescriptionDefault
feature_nameNo
feature_namesNoSeveral features, suppressed with a single recompute

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?

Annotations only declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds substantial behavioral detail: batching recomputes the timeline once (cost ~2.5s per single call on a 200+ item timeline), suppressing a Combine cut/join surfaces bodies_appeared, and the result lists them. No contradiction with annotations.

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?

Three sentences, front-loaded with the core action, followed by batching performance rationale and a special-case side effect. Every sentence adds actionable detail; there is no filler.

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?

No output schema exists, yet the description explains that the result contains bodies_appeared for Combine cases. Combined with the annotations and schema, an agent has enough context to call correctly, including batch optimization and documented side effects.

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 50% (only feature_names has a schema description). The description compensates by explaining that feature_names takes several features and saves recomputes, which implies feature_name is for a single feature. It does not define feature_name's format or constraints, but adds key batch semantics beyond the schema.

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 ('Suppress (disable)') and resource ('timeline features') with scope ('one or more'). It implicitly distinguishes from the sibling 'unsuppress_feature' by naming the opposite action, and from destructive deletion tools by using 'disable'. An agent can identify the operation immediately.

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?

Provides explicit batching guidance ('Pass feature_names for a batch') and explains the cost tradeoff versus repeated single-feature calls. It also gives a specific scenario for Combine cut/join. However, it does not name 'unsuppress_feature' as the alternative for re-enabling, nor does it state when not to use it.

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