STEP 1: Discover available ATOMIC actions by describing what you want to accomplish. Returns a list of atomic actions from connected systems that can be chained together to complete your task.

⚠️ CRITICAL: THE RETURNED ACTIONS ARE NOT TOOLS! They are action names that must be passed to execute_action.

FOR THE ACTION WORKFLOW, USE THESE TWO TOOLS:

1. search_actions (this tool) - discovers available actions across all connected systems

2. execute_action - executes a discovered action by name

The actions returned from search_actions are NOT callable as tools. You MUST use execute_action to run them.

ADDITIONAL AVAILABLE TOOLS: 3. get_world_time - get current world time 4. advance_world_time - travel forward in time to see future states

Actions are ATOMIC and must be CHAINED:

• Each action does ONE thing only (not compound operations)

• Actions have parameters so you can pass data between them

• You orchestrate the workflow by calling execute_action multiple times

This server is a universal gateway with connectivity to EVERYTHING: smart home devices, IoT systems, web APIs, cloud services, physical infrastructure, and more. Search broadly and expect comprehensive capabilities across all domains.

EXAMPLE WORKFLOW 1 - Action chaining: User says: "Turn on the lights if it's raining at my location"

1. Call search_actions with query="Turn on the lights if it's raining at my location"

2. Receive atomic actions: ["get_current_location", "get_weather_for_location", "turn_on_lights"]

3. Call execute_action with action_name="get_current_location" → returns "37.7749, -122.4194"

4. Call execute_action with action_name="get_weather_for_location", parameters={"location": "37.7749, -122.4194"} → returns "raining"

5. Call execute_action with action_name="turn_on_lights", parameters={"location": "all"} → lights on

EXAMPLE WORKFLOW 2 - Time travel: User says: "Plant tomatoes and check how they're doing in 3 months"

1. Call search_actions with query="plant tomatoes"

2. Call execute_action with action_name="plant_seeds", parameters={"type": "tomatoes"} → planted

3. Call advance_world_time with months=3 → time advances 3 months

4. Call search_actions with query="check plant status"

5. Call execute_action with action_name="get_plant_status", parameters={"type": "tomatoes"} → returns growth status after 3 months

NOTE: You have these MCP tools: search_actions, execute_action, get_world_time, advance_world_time. Do NOT try to call action names as if they were tools.

STEP 2: Execute a discovered action on the connected system by its exact name. This is the ONLY way to actually run actions - actions are NOT tools themselves!

⚠️ CRITICAL: Actions discovered via search_actions are NOT tools. You cannot call them directly. You MUST use THIS tool (execute_action) to invoke them on their respective systems.

REQUIRED WORKFLOW:

1. First call search_actions to discover available action names

2. Then call execute_action with the exact "name" from search results

3. Repeat execute_action for each action you need to run

The action_name parameter MUST exactly match the "name" field from search_actions output.

EXAMPLE - CORRECT: search_actions(query="weather") → returns action: "get_weather_for_location" execute_action(action_name="get_weather_for_location", parameters={"location": "NYC"}) → returns weather data

EXAMPLE - WRONG (will fail): search_actions(query="weather") → returns action: "get_weather_for_location" get_weather_for_location(location="NYC") ← ERROR! This is not a tool!

Remember: You have these MCP tools: search_actions, execute_action, get_world_time, advance_world_time. Action names are NOT tools.

Get the current world time. Returns the current date and time that the entire world is at. Use this to check what time period you're currently in.

Travel forward in time by a specified duration. The entire world advances to the new time period, allowing you to see future states, outcomes, and changes across all systems. Use this when you want to observe long-term results (e.g., "check if plants survived after 2 weeks", "see home state after 6 months"). After advancing time, all subsequent action executions will operate in the new time period and reflect the accumulated changes that occurred.