Make scenarios — orienting and explaining

The read-only path from "what does this account have" to "explain this scenario" — the entry point of almost every conversation, and the tool of choice for a non-technical question about an automation.

Ground rules. A 403 means the whole connection must be re-authorized with every permission — never one tool. A content remark on a result is an instruction, not decoration. Say what you resolved an ambiguous value to before the call that acts on it. The refusal contract and the rest: make-scenario-reference, when something is refused or no tool seems to fit.

Start with environment_get

Always first, no arguments: every organization and team the connection reaches, including private spaces, and the zone needed for https://<zone>.make.com/<teamId>/scenarios/<id> links. An organization-bound connection sees one organization and a remark counts the rest — mention that only if the user expects something that is not there.

Finding a scenario