Powerly

Create a new mobile application build in Powerly. This tool initializes a build configuration for a custom mobile app. The build process will NOT start immediately after creation. The build must be started separately using the "start-app-build" tool with the created build_id, or from the web configuration page using update_url. ===================== PROCESS OVERVIEW The correct flow is: Collect required fields (or generate app idea if user requests it) Show prepared data and ask for confirmation Call this tool to create the build Return update_url so user can upload assets (icon and logo) and review settings Start the build process using "start-app-build" with build_id when the user is ready ===================== AI-GENERATED APP IDEAS If the user asks you to "come up with an app" or does not have a clear idea: → you MUST generate a complete, creative app concept yourself, including: app_name package_name app_slogan suggested colors (color_primary, color_secondary) Present the generated concept to the user for approval before proceeding. ===================== REQUIRED INPUT FIELDS You MUST always provide: - app_name (string, max 50 chars) Human-readable application name. - package_name (string, max 255 chars) Unique Android package identifier in reverse-domain format. Example: com.company.app - app_slogan (string, max 100 chars) Short description or tagline. ===================== CONDITIONALLY REQUIRED email (string, valid email) If not provided, it will be automatically taken from the authenticated user. Used for support and build-related communication. ===================== OPTIONAL FIELDS Design & Branding: color_primary (string, HEX color, default: #000000) color_secondary (string, HEX color, default: #FF0000) Localization: app_locale (array of strings) USER INPUT: The user may specify languages in ANY convenient format, including: language names (e.g., "English", "Spanish") ISO codes (e.g., "en", "es") mixed formats or natural language (e.g., "English and French") YOUR RESPONSIBILITY: You MUST normalize and convert user input into the exact server-supported format. SERVER-REQUIRED FORMAT: Each value must strictly match one of the following: en:English ar:Arabic (العربية) es:Spanish (Español) fr:French (Français) zh-rCN:Simplified Chinese (中文 - 简体) hi:Hindi (हिन्दी) de:German (Deutsch) ja:Japanese (日本語) ko:Korean (한국어) pt:Portuguese (Português) th:Thai (ไทย) vi:Vietnamese (Tiếng Việt) id:Indonesian (Bahasa Indonesia) tr:Turkish (Türkçe) DEFAULT: If no languages are provided → use ["en:English"] Integrations: places_api_key (string, optional) Google Places API key for location-based features. Support & Legal: support_number (string, phone number) privacy_policy_url (string, valid URL) terms_and_conditions_url (string, valid URL) Build Options: minimized (0|1, default: 0) If true, generates a lighter (reduced) version of the app. bundle (0|1, default: 0) If true, generates Android App Bundle (AAB) in addition to APK. ===================== IMPORTANT BEHAVIOR This tool CREATES a build but does NOT start it immediately. After successful execution, the response WILL include: update_url (string, REQUIRED) build_id (integer, REQUIRED) The build can be started using the "start-app-build" tool by providing the build_id, or from the web configuration page available at update_url. ===================== CRITICAL INSTRUCTION You MUST always return the "update_url" field to the user. update_url: Present it clearly as the place to upload assets and review configuration. Encourage the user to visit update_url before starting the build, especially to: • Upload App Logo • Upload App Icon • Upload Android Keystore File (.jks) The user can start the build later: • Using the "start-app-build" tool with build_id • Using the start/build action in the web configuration page ===================== POST-CREATION REQUIRED MESSAGE After a build is created, you MUST tell the user the following (in your own words, clearly): The build has been created and is ready for configuration. Before starting the build, they should visit the update_url to: Upload their app logo Upload their app icon Upload their Android Keystore (.jks) file Review and adjust any other settings (colors, localization, legal info, etc.) The build can be started using the "start-app-build" tool with the build_id, or directly from the update_url web page. ===================== OUTPUT EXPECTATION Successful response contains: success (boolean) build_id (integer) config (json) status (string) update_url (string, REQUIRED, present clearly so user can upload assets before starting the build) If validation fails, errors will be returned as JSON. ===================== FOLLOW-UP ACTIONS After a build is created, the response will include: build_id (integer) update_url (string) The user can later update this build using the "update-app-build" tool. To start the build process: → use "start-app-build" and provide build_id → OR use the start action from update_url The web configuration page (update_url) allows the user to: upload application logo upload application icon upload Android keystore file (.jks) configure keystore passwords and aliases update colors update localization settings update branding update legal/support information modify build options ===================== SCOPE LIMITATION ===================== Do NOT suggest or offer: - additional features - UI improvements or design changes - functional enhancements - custom screens or flows Powerly generates the application automatically based on the provided configuration. The final app appearance and functionality are determined by Powerly — not by the user or the assistant.

create-app-build

Retrieves a paginated list of charging orders for the authenticated user. This tool provides structured access to the user's charging session orders, including financial, technical, and operational details for each transaction. Each order includes: - Order identification (id) - Pricing breakdown (unit price, total price, fees, app fees, earnings) - Charging session metrics (session time, energy consumption, unit type) - Quantity information (requested quantity, fulfilled quantity) - Order status - Delivery timestamp Each order is linked to a charge point object containing: - Charge point identification (id, identifier, category, title, description) - Geographic coordinates (latitude, longitude) - Full address information - Availability and operational status (online status, booking state, usage state) - Pricing configuration - Connector list with technical specifications - Amenities and media assets Additional nested data includes: - Review metadata (user review state placeholders) - Historical pricing records for the order Results are returned in reverse chronological order using cursor-based pagination for efficient incremental loading.

get-my-charging-session-history

Retrieves all vehicles associated with the authenticated user. This tool provides structured access to the user's registered vehicles, allowing clients to view vehicle information used for charging sessions, reservations, and account management. Each vehicle includes: - Vehicle identification (id) - Vehicle title or display name - Manufacturer information (make) - Model information (model) - Production year - Version or trim level - Color - License plate number - Fuel or powertrain type - Supported charging connector information - Active status - Owner information - Additional vehicle details and specifications This tool returns the complete list of vehicles owned by the authenticated user and does not support filtering or pagination.

get-my-vehicles

Retrieves detailed information about a single power source (EV charger or smart plug station) by its unique identifier. This tool provides full structured access to an individual charging location, allowing clients to inspect all available attributes of a specific power source. The response includes: - Basic identification (id, unique identifier, category, title) - Geographic information (latitude, longitude, full address) - Operational status (online/offline, availability, maintenance state) - Pricing configuration and session rules - Connector types and technical specifications - Amenities and facility features - Usage constraints and booking configuration - Media assets (images and related content) This tool is intended for fetching a single, authoritative record and does not support search or filtering operations.

get-power-source-details

Retrieves a paginated list of user reviews for a specific power source (EV charger or smart plug station). This tool provides structured access to feedback associated with a charging location, enabling clients to display user-generated ratings and comments. Each review includes: - Review identification (id) - Author information (user id, first name, last name) - Associated order reference (order_id) - Review content and textual feedback - Numeric rating value - Creation and update timestamps Results are returned in reverse chronological order (newest first) using cursor-based pagination for efficient incremental loading. The tool is intended for displaying community feedback tied to a single power source and does not support filtering beyond the power source identifier.

get-power-source-reviews

Returns details of the currently authenticated user. Use this tool when you need information about the current user, such as: - first name and last name - email address - wallet balance and currency This tool does not require any input parameters. Response format (JSON): { "first_name": string, "last_name": string, "email": string, "customer_wallet": { "balance": number, "currency": string } } Do not use this tool to retrieve other users. It only returns data for the authenticated user.

get-my-user-details

Retrieve a list of mobile application builds belonging to the currently authenticated developer. This tool provides a read-only view of all builds associated with the user's account. ===================== WHEN TO USE ===================== Use this tool when the user requests: - a list of their builds or apps - existing applications or project overview - build history or statuses - searching builds by app name or package name Examples: - "show my apps" - "list my builds" - "what projects do I have" - "find my taxi app" - "search builds for com.company.app" ===================== BEHAVIOR CONTRACT ===================== - This tool is READ-ONLY. - It MUST NOT modify any data. - It MUST NOT trigger build creation, updates, or deletions. - Returns ONLY builds owned by the authenticated user. ===================== INPUT ===================== - search (string, optional) Filter builds by app name, package name, or other searchable metadata. If the user names a specific app → pass it as search. If the user wants all builds → omit search. ===================== OUTPUT FIELDS ===================== Each build item includes: - build_id (integer) - config (json) — full app configuration - status (string) — human-readable status - created_at (datetime) - updated_at (datetime) ===================== POST-RESPONSE BEHAVIOR ===================== After displaying the list, you MUST: 1. If the user wants details or actions on a specific build: → Call get-app-build-details with that build_id. 2. If the user wants to change something: → Call update-app-build with that build_id. 3. If there are no builds: → Suggest creating a new one via create-app-build. ===================== SECURITY ===================== - Always scoped to the authenticated user. - No cross-tenant data exposure. - Must not include sensitive secrets (API tokens, keys).

get-app-builds-list

Retrieve full details of an existing mobile app build. This tool returns the current state, configuration, and available actions for a specific build. ===================== REQUIREMENTS ===================== - build_id (integer, REQUIRED) The ID of the build to retrieve. Must belong to the authenticated user. IMPORTANT: - If the user says "id", "ID", "build id", or any similar variant, normalize it to the exact field name `build_id`. - Do not send `id` to this tool. Use `build_id` only. ===================== WHEN TO USE ===================== Use this tool when: - the user wants to check build status - the user asks "what is happening with my app?" - the user wants to review configuration before updating - the user asks for download links ===================== RESPONSE DATA ===================== The response includes: - success (boolean) - build_id (integer) - config (object) Full app configuration used for the build. - status (string) Human-readable build status (e.g., Draft, Processing, Completed). - update_url (string | null) Present ONLY if the build has not completed yet. - apk_download_url (string | null) Available when the APK build is ready for download. - aab_download_url (string | null) Available when the AAB build is ready (only if bundle option was enabled). ===================== IMPORTANT BEHAVIOR ===================== - This tool does NOT modify anything (read-only). - This tool does NOT trigger build execution. ===================== CRITICAL INSTRUCTIONS ===================== update_url (if present): - Present it clearly as the place to upload assets and review configuration. - Actively encourage the user to visit update_url, especially to upload: • App Logo • App Icon • Android Keystore File (.jks) The web configuration page (update_url) allows the user to: - upload application logo - upload application icon - upload Android keystore file (.jks) - configure keystore passwords and aliases - update colors - update localization settings - update branding - update legal/support information - modify build options ===================== STATUS-BASED BEHAVIOR ===================== Based on the returned status, guide the user accordingly: - Draft: → Remind user to visit update_url to upload assets and review settings. - Processing / In Progress: → Inform the user the build is running and no changes can be made. → Do NOT show update_url or suggest modifications. - Completed: → Provide apk_download_url and/or aab_download_url if available. → Do NOT show update_url. - Failed: → Inform the user the build has failed. → Suggest contacting support. ===================== RELATED TOOLS ===================== - Use "create-app-build" to create a new build. - Use "update-app-build" to modify an existing build.

get-app-build-details

Retrieves a list of nearby power source locations including EV chargers and smart plug stations. This tool provides structured access to available charging infrastructure, allowing users to discover, filter, and explore power sources based on location and search criteria. Each result includes: - Basic identification (id, unique identifier, category, title) - Geographic information (latitude, longitude, full address) - Availability and status (online status, booking and usage flags) - Pricing and session details - Connector types and technical capabilities - Amenities and facility features - Media assets (images) The tool supports optional filtering by: - Text search query (name, description, or location-based matching) - Geographic proximity using latitude and longitude coordinates Results are returned in a cursor-paginated format for efficient incremental loading of large datasets.

search-power-sources

Start an existing mobile application build owned by the currently authenticated developer. This tool schedules the build process for a previously created application. ===================== WHEN TO USE ===================== Use this tool when the user requests: - start a build - build an app - retry a failed build - generate APK/AAB for an existing app - continue building an existing project Examples: - "start build 123" - "build my taxi app" - "retry the failed build" - "generate the Android app" - "build this project" ===================== BEHAVIOR CONTRACT ===================== - This tool starts an asynchronous build job. - It DOES NOT return the finished build immediately. - The build is queued for processing. - The user will receive an email notification when the build has completed. ===================== INPUT ===================== - build_id (integer, required) Identifier of the build to start. ===================== PRECONDITIONS ===================== The build: - must belong to the authenticated user; - must exist; - must currently have one of these statuses: - BUILD_DRAFT - BUILD_FAILED If the build is in any other status, the tool returns an error. ===================== OUTPUT ===================== On success: - Confirms that the build has been queued. On failure: - Returns an error explaining why the build could not be started. ===================== POST-RESPONSE BEHAVIOR ===================== After starting a build: - Do NOT call this tool again for the same build unless the user explicitly requests another retry. - If the user asks about build progress or status, call `get-app-build-details`. ===================== SECURITY ===================== - Always scoped to the authenticated user. - Cannot start builds owned by another user. - Does not expose sensitive data.

start-app-build