genai-toolbox/docs/en/resources/tools/looker/looker-query-sql.md at d013badbdace895d9cbb5572b85d3fffa8917187

mirror of https://github.com/googleapis/genai-toolbox.git synced 2026-04-09 03:02:26 -04:00

Files

Yuan Teoh 293c1d6889 feat!: update configuration file v2 (#2369 )

This PR introduces a significant update to the Toolbox configuration
file format, which is one of the primary **breaking changes** required
for the implementation of the Advanced Control Plane.

# Summary of Changes
The configuration schema has been updated to enforce resource isolation
and facilitate atomic, incremental updates.
* Resource Isolation: Resource definitions are now separated into
individual blocks, using a distinct structure for each resource type
(Source, Tool, Toolset, etc.). This improves readability, management,
and auditing of configuration files.
* Field Name Modification: Internal field names have been modified to
align with declarative methodologies. Specifically, the configuration
now separates kind (general resource type, e.g., Source) from type
(specific implementation, e.g., Postgres).

# User Impact
Existing tools.yaml configuration files are now in an outdated format.
Users must eventually update their files to the new YAML format.

# Mitigation & Compatibility
Backward compatibility is maintained during this transition to ensure no
immediate user action is required for existing files.
* Immediate Backward Compatibility: The source code includes a
pre-processing layer that automatically detects outdated configuration
files (v1 format) and converts them to the new v2 format under the hood.
* [COMING SOON] Migration Support: The new toolbox migrate subcommand
will be introduced to allow users to automatically convert their old
configuration files to the latest format.

# Example
Example for config file v2:
```
kind: sources
name: my-pg-instance
type: cloud-sql-postgres
project: my-project
region: my-region
instance: my-instance
database: my_db
user: my_user
password: my_pass
---
kind: authServices
name: my-google-auth
type: google
clientId: testing-id
---
kind: tools
name: example_tool
type: postgres-sql
source: my-pg-instance
description: some description
statement: SELECT * FROM SQL_STATEMENT;
parameters:
- name: country
  type: string
  description: some description
---
kind: tools
name: example_tool_2
type: postgres-sql
source: my-pg-instance
description: returning the number one
statement: SELECT 1;
---
kind: toolsets
name: example_toolset
tools:
- example_tool
```

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Averi Kitsch <akitsch@google.com>

2026-01-27 16:58:43 -08:00

1.8 KiB

Raw Blame History

title, type, weight, description, aliases

title

type

weight

description

aliases

looker-query-sql

docs

"looker-query-sql" generates a sql query using the Looker semantic model.

/resources/tools/looker-query-sql

About

The looker-query-sql generates a sql query using the Looker semantic model.

It's compatible with the following sources:

looker

looker-query-sql takes eight parameters:

the model
the explore
the fields list
an optional set of filters
an optional set of pivots
an optional set of sorts
an optional limit
an optional tz

Starting in Looker v25.18, these queries can be identified in Looker's System Activity. In the History explore, use the field API Client Name to find MCP Toolbox queries.

Example

kind: tools
name: query_sql
type: looker-query-sql
source: looker-source
description: |
  This tool generates the underlying SQL query that Looker would execute
  against the database for a given set of parameters. It is useful for
  understanding how Looker translates a request into SQL.

  Parameters:
  All parameters for this tool are identical to those of the `query` tool.
  This includes `model_name`, `explore_name`, `fields` (required),
  and optional parameters like `pivots`, `filters`, `sorts`, `limit`, and `query_timezone`.

  Output:
  The result of this tool is the raw SQL text.

Reference

field	type	required	description
type	string	true	Must be "looker-query-sql"
source	string	true	Name of the source the SQL should execute on.
description	string	true	Description of the tool that is passed to the LLM.

1.8 KiB Raw Blame History

About

Example

Reference

1.8 KiB

Raw Blame History