Registers a Git repository in MetaCall FaaS so it can be deployed as a serverless function. Use this tool when the user wants to deploy code directly from a repository instead of uploading a zip file. Requires the repository URL and branch name. Returns the repository identifier that will later be used for deployments.

Invoke an asynchronous function from a deployed MetaCall service. Use this tool when the function returns a Promise, coroutine, or async result. Arguments must be provided as an object where keys match the function parameter names (e.g., async_add(a,b) → {"a":1,"b":2}). If required arguments are missing, ask the user for them before invoking.

Retrieves the list of branches available in a Git repository. Use this tool when you need to determine which branch should be inspected, deployed, or used for repository-based deployments. Requires the repository URL as input and returns all available branch names.

Invoke a synchronous function from a deployed MetaCall service. Arguments must be provided as an object where keys match the function parameter names (e.g., add(a,b) → {"a":1,"b":2}). If required arguments are missing, ask the user for them.

Deploy a package or repository to MetaCall Cloud. CRITICAL PREREQUISITE: MetaCall only allows ONE deployment per subscription plan (Essential, Standard, Premium). Before executing this deployment, you MUST check the user's currently active deployments and subscriptions to find an unused plan. If you attempt to deploy on a plan that is already in use, it will fail. Parameters: - name: - For ResourceType.Package -> package name - For ResourceType.Repository -> The exact "id" returned by the Add repository tool. Do NOT use the Git URL. - plan: An available, UNUSED subscription plan (Essential, Standard, or Premium). - release: branch name (e.g. main) - version: deployment version (e.g. v1)

Deletes an existing deployment and its associated package from MetaCall FaaS. Use this tool when the user wants to remove a deployed service or clean up an existing deployment. Requires the deployment suffix and optionally the version. This operation permanently removes the deployment and its resources from the MetaCall platform.

Checks whether the current MetaCall account is allowed to deploy serverless functions. Use this tool before attempting to upload or deploy packages to ensure the account has deployment permissions enabled. Returns a boolean indicating whether deployments are permitted for the authenticated account.

Lists the files available in a specific branch of a Git repository. Use this tool when you need to inspect the files of a repository branch, verify the presence of certain files, or explore the repository structure before deploying or analyzing code. Requires the repository URL and branch name, and returns the list of file paths found in that branch.

Retrieves all deployments available in the current MetaCall FaaS account. Use this tool when you need to discover existing deployed services, identify deployment suffixes, or inspect available deployments before invoking functions, retrieving logs, or deleting deployments. Returns a list of deployments associated with the authenticated account.

Retrieves detailed information about a specific MetaCall deployment using its suffix. Use this tool when the deployment suffix is already known and you need to inspect its configuration, metadata, or runtime details. If the suffix is unknown, use the 'inspect' tool first to list all available deployments.

Retrieves all subscription plans available in the MetaCall account and shows how many deployments are currently using each plan. Use this tool when you need to understand available plans or check current plan usage before deploying.

Retrieves deployments associated with the account's billing subscriptions. Use this tool to see which deployments are currently linked to subscription plans.

Retrieve logs from a MetaCall deployment container. The container usually matches the runtime language used in the deployment (e.g., python, node).Use this tool when debugging a deployment or checking runtime output.

Validates the current MetaCall authentication token used to access the MetaCall FaaS API. Use this tool when you need to confirm that the authentication token is still valid before performing operations such as deploying packages, invoking serverless functions, or retrieving account information. Returns a boolean indicating whether the token is valid.