Skip to main content
Glama

get_fusion_comp

Read-only

Inspect a Fusion composition's name, type, flow position, connected main inputs, and render range before editing it with execute_python.

Instructions

Tools of a Fusion composition (name, type, position in the flow, main inputs connected) and its render range. Edit it with execute_python via ctx.comp(':').

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

Input Schema

NameRequiredDescriptionDefault
compNo
itemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context by naming the mutation path (execute_python / ctx.comp) and by enumerating what is returned, but says nothing about failure modes when the item has no comp, or about the size/shape of the returned tool list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the returned data front-loaded and the editing escape hatch second. Minor awkwardness in 'Tools of a Fusion composition' (it reads as a list of nodes, not 'tools of'), but nothing is wasted.

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?

With no output schema and 0% parameter coverage, the description carries the full burden, yet it explains neither parameter's meaning nor the addressing format needed to call it correctly. It partially compensates by listing returned fields, but an agent still cannot confidently supply 'item' or 'comp' from this text alone.

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% for both parameters. The description never mentions 'item' (presumably the timeline item owning the comp) or 'comp' (a string-or-integer selector defaulting to 1); the ctx.comp('<uid>:<n>') notation hints at a uid:index addressing scheme but is not tied to either parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource and the returned content concretely: the tools of a Fusion composition (name, type, position in the flow, connected main inputs) plus its render range. The verb is only implied by the 'get_' prefix, but the enumerated return fields make the purpose unambiguous and separable from fusion_comps or get_node_graph.

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 second sentence gives a real routing hint: to modify the comp, use execute_python with ctx.comp('<uid>:<n>') rather than this tool. However, it never says when to prefer this over fusion_comps (listing comps) or get_node_graph, so the read-side alternative selection is 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