StatelessServer

Showing 25 of 35 from the live probe.

• List Repositories

  List the Dataform repositories in a given Google Cloud project and location. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}`.

• Create Repository

  Create a new Dataform repository in a given Google Cloud project and location. This tool establishes the root resource required for all other transformation assets, such as compilation results and workflow configurations. A repository must be created before any other Dataform MCP tool can be used. Enabling this tool is the first step in setting up a Dataform project. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}`. The `repository_id` parameter

• Commit Repository Changes

  Apply a Git commit to record the state of files within a Dataform repository. This tool is primarily intended for managing single-file assets—such as notebooks or saved queries—that reside directly in the repository. This tool isn't used in typical pipeline workflows that require workspaces. Don't use this tool on repositories connected to a remote Git host. To verify, use the `get_repository` tool. If the `git_remote_settings` field is present, the repository is connected to a remote host and

• Read Repository File

  Return the contents of a file that's inside a Dataform repository. This tool isn't for standard pipeline development. It's intended for direct repository interaction, typically for managing single-file assets such as notebooks or saved queries. Don't use this tool on repositories connected to a remote Git host. To verify, use the `get_repository` tool. If the `git_remote_settings` field is present, the repository is connected to a remote host and you must use the `read_file` tool to read the f

• Query Repository Directory Contents

  Return the contents of a given Dataform repository directory. This tool is primarily used to list and manage single-file assets directly in the repository. Don't use this tool on repositories connected to a remote Git host. To verify, use the `get_repository` tool. If the `git_remote_settings` field is present, the repository is connected to a remote host and you must use the `query_directory_contents` tool to list a workspace directory instead. The `name` parameter value refers to the reposi

• List Workflow Configs

  List the workflow configurations in a given Dataform repository. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`.

• Get Workflow Config

  Fetch a single Dataform workflow configuration. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/workflowConfigs/{workflow_config}`.

• Create Workflow Config

  Create a new workflow configuration in a given Dataform repository. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`. The `workflow_config_id` is the ID for the workflow configuration. A workflow configuration pairs a `ReleaseConfig` with a schedule and an identity. The `ReleaseConfig` determines which code is compiled, while this tool determines when that code runs and which service account runs it. Prerequisite: You m

• Update Workflow Config

  Update the properties of an existing Dataform workflow configuration, such as its execution schedule (cron), associated release configuration, or invocation overrides. Modifications to the `cron_schedule` take effect immediately for all future scheduled executions. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/workflowConfigs/{workflow_config}`. The `workflow_config.release_config` parameter value is strictly required fo

• List Release Configs

  List the release configurations in a given Dataform repository. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`.

• Get Release Config

  Fetch a single Dataform release configuration. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/releaseConfigs/{release_config}`.

• Create Release Config

  Create a new release configuration in a given Dataform repository. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`. The `release_config_id` is the user-defined ID for the release configuration. If the user doesn't specify an ID, generate a short, descriptive ID using lowercase letters, numbers, and hyphens based on their request. Omit the `release_config.cron_schedule` parameter value for Google-hosted repositories. To

• Update Release Config

  Update an existing Dataform release configuration, which serves as a template for automatic code compilation. Updates to fields like `git_commitish` change how future compilation results are generated, but such updates don't retroactively alter existing `CompilationResult` assets. Omit the `release_config.cron_schedule` parameter value when updating Google-hosted repositories. To verify, use the `get_repository` tool. If the `git_remote_settings` field is missing, the repository is Google-host

• Create Compilation Result

  Create a new Dataform compilation result in a given Google Cloud project and location. This tool compiles `.sqlx` files into executable SQL. Agents need to know that subsequent code changes aren't reflected in this result unless a new compilation is triggered. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`. Agents can validate the compiled SQL by inspecting `CompilationResultAction` resources and potentially using a Bi

• List Workflow Invocations

  List the workflow invocations in a given Dataform repository. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`.

• Create Workflow Invocation

  Create a new workflow invocation in a given Dataform repository. The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`. Either the `compilation_result` or the `workflow_config` parameter value is required. * If using `compilation_result`, the parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/compilationResults/{compilation_result}`. * If using `workflow_config`, the

• Cancel Workflow Invocation

  Request the graceful termination of a running Dataform workflow invocation. This tool sends a cancellation signal to the running workflow. However, any individual BigQuery jobs, table creations, or assertions that have already completed as part of this workflow will not be rolled back. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/workflowInvocations/{workflow_invocation}`.

• Get Compilation Result

  Fetch a single Dataform compilation result. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/compilationResults/{compilation_result}`.

• Query Compilation Actions

  Return the compilation result actions for a given Dataform compilation result. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/compilationResults/{compilation_result}`.

• Query Workflow Invocation Actions

  Return the workflow invocation actions for a given Dataform workflow invocation. These actions represent the individual BigQuery jobs, table creations, or assertions that make up the workflow. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/workflowInvocations/{workflow_invocation}`.

• Get Workflow Invocation

  Fetch a single Dataform workflow invocation. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/workflowInvocations/{workflow_invocation}`.

• List Workspaces

  List the development workspaces in a given Dataform repository. Use this tool to discover existing workspaces before performing file operations (using tools such as `read_file` or `write_file`) or committing code (using a tool such as `commit_workspace_changes`). The `parent` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}`.

• Get Workspace

  Fetch a single Dataform development workspace. The `name` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/workspaces/{workspace}`. If you don't know the exact workspace name, use the `list_workspaces` tool to find it.

• Create Workspace

  Create a new development workspace in a given Dataform repository. A workspace is an isolated, editable checkout of the repository. Use a workspace when you need to author or revise pipeline code across several files and validate it before committing. Edit files in the workspace with the `write_file` and `remove_file` tools, record the result with the `commit_workspace_changes` tool, and publish the committed changes to the repository with the `push_git_commits` tool. Don't use the `commit_rep

• Query Directory Contents

  Return the contents of a given directory inside a Dataform workspace. Use this tool to discover valid file paths before calling the `read_file` or `write_file` tools. The `workspace` parameter value must be in the format `projects/{project_id}/locations/{location}/repositories/{repository}/workspaces/{workspace}`. The `path` parameter value is the relative path to the directory from the workspace root. Don't use directory traversal, such as `..`. If omitted, the workspace root is used.