765T Flow

Most tools have clearly distinct roles: flow_call executes, flow_find searches semantically, flow_get reads a specific ref, flow_list_instances enumerates instances, flow_read_result reads parted answers, and flow_report_issue handles feedback. The one soft overlap is discovery: flow_tools (browse catalog/schema by exact name) and flow_find (natural-language tool search) both surface tools, and flow_get vs flow_tools both retrieve tool information, so an agent must read carefully to pick the right entry point.

All names use a consistent flow_ prefix with snake_case, which is highly predictable. The only deviation is that flow_tools is a bare noun rather than the verb_noun pattern used by flow_call, flow_find, flow_get, flow_list_instances, flow_read_result, and flow_report_issue.

Seven tools is well-scoped for a meta-gateway that fronts a large dynamic Revit catalog: discovery, schema lookup, execution, result reading, instance listing, and reporting each earn their place without enumerating the catalog itself.

The surface covers the full gateway lifecycle: find/list tools, read schemas, list instances, execute calls, read parted results, and report issues. Minor gaps exist (e.g. no call status/cancellation or history/account operations), but core Revit workflows via the catalog are reachable.