RFix

Tools

Token cost is the o200k count of the tools list JSON, including schemas, before any tool is called.

• rfix_plan_scenario

  ALWAYS call this first for any RF scenario request. Returns block schemas, composition rules, constraints, and a reference example payload. YOU must compose your own graph/project using this guidance,

• rfix_list_blocks

  Search the shipped RFIX block catalog by keyword. Use this when you need to find specific block types not already returned by rfix_plan_scenario. Queries like radar, ship, aircraft, communication, 3d,

• rfix_list_capabilities

  List high-level RFIX capability families for planning without flooding context. Use this before block search when the request is broad, then call rfix_search_block_catalog for likely concrete node typ

• rfix_search_block_catalog

  Search concrete RFIX node types by natural-language keywords without returning full parameter schemas. Use this before constructing add_node actions, then call rfix_get_block_details for the selected

• rfix_get_block_details

  Return full parameter schemas and add-node templates for a small selected set of RFIX nodeTypes. Call this only after rfix_search_block_catalog has narrowed the relevant blocks.

• rfix_export_rfix_project

  Convert RFIX JSON input into an importable `.rfix.gz` project file. `payload` may be an RFIX backend payload, GCF prompt graph output, exported graph data, or editor/.rfix-style project JSON. Project-