Tools on MCP Toolbox for Databases

looker-add-dashboard-element

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-add-dashboard-element tool creates a new tile (element) within an existing Looker dashboard. Tiles are added in the order this tool is called for a given dashboard_id.

CRITICAL ORDER OF OPERATIONS:

Create the dashboard using make_dashboard.
Add any dashboard-level filters using add_dashboard_filter.
Then, add elements (tiles) using this tool.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: add_dashboard_element
type: looker-add-dashboard-element
source: looker-source
description: |
 This tool creates a new tile (element) within an existing Looker dashboard.
 Tiles are added in the order this tool is called for a given `dashboard_id`.

 CRITICAL ORDER OF OPERATIONS:
 1. Create the dashboard using `make_dashboard`.
 2. Add any dashboard-level filters using `add_dashboard_filter`.
 3. Then, add elements (tiles) using this tool.

 Required Parameters:
 - dashboard_id: The ID of the target dashboard, obtained from `make_dashboard`.
 - model_name, explore_name, fields: These query parameters are inherited
 from the `query` tool and are required to define the data for the tile.

 Optional Parameters:
 - title: An optional title for the dashboard tile.
 - pivots, filters, sorts, limit, query_timezone: These query parameters are
 inherited from the `query` tool and can be used to customize the tile's query.
 - vis_config: A JSON object defining the visualization settings for this tile.
 The structure and options are the same as for the `query_url` tool's `vis_config`.

 Connecting to Dashboard Filters:
 A dashboard element can be connected to one or more dashboard filters (created with
 `add_dashboard_filter`). To do this, specify the `name` of the dashboard filter
 and the `field` from the element's query that the filter should apply to.
 The format for specifying the field is `view_name.field_name`.

Reference

field	type	required	description
type	string	true	Must be “looker-add-dashboard-element”.
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.

looker-add-dashboard-filter

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-add-dashboard-filter tool adds a filter to a specified Looker dashboard.

CRITICAL ORDER OF OPERATIONS:

Create a dashboard using make_dashboard.
Add all desired filters using this tool (add_dashboard_filter).
Finally, add dashboard elements (tiles) using add_dashboard_element.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Parameters

parameter	type	required	default	description
dashboard_id	string	true	none	The ID of the dashboard to add the filter to, obtained from `make_dashboard`.
name	string	true	none	A unique internal identifier for the filter. This name is used later in `add_dashboard_element` to bind tiles to this filter.
title	string	true	none	The label displayed to users in the Looker UI.
filter_type	string	true	`field_filter`	The filter type of filter. Can be `date_filter`, `number_filter`, `string_filter`, or `field_filter`.
default_value	string	false	none	The initial value for the filter.
model	string	if `field_filter`	none	The name of the LookML model, obtained from `get_models`.
explore	string	if `field_filter`	none	The name of the explore within the model, obtained from `get_explores`.
dimension	string	if `field_filter`	none	The name of the field (e.g., `view_name.field_name`) to base the filter on, obtained from `get_dimensions`.
allow_multiple_values	boolean	false	true	The Dashboard Filter should allow multiple values
required	boolean	false	false	The Dashboard Filter is required to run dashboard

Example

kind: tool
name: add_dashboard_filter
type: looker-add-dashboard-filter
source: looker-source
description: |
 This tool adds a filter to a Looker dashboard.

 CRITICAL ORDER OF OPERATIONS:
 1. Create a dashboard using `make_dashboard`.
 2. Add all desired filters using this tool (`add_dashboard_filter`).
 3. Finally, add dashboard elements (tiles) using `add_dashboard_element`.

 Parameters:
 - dashboard_id (required): The ID from `make_dashboard`.
 - name (required): A unique internal identifier for the filter. You will use this `name` later in `add_dashboard_element` to bind tiles to this filter.
 - title (required): The label displayed to users in the UI.
 - filter_type (required): One of `date_filter`, `number_filter`, `string_filter`, or `field_filter`.
 - default_value (optional): The initial value for the filter.

 Field Filters (`flter_type: field_filter`):
 If creating a field filter, you must also provide:
 - model
 - explore
 - dimension
 The filter will inherit suggestions and type information from this LookML field.

Reference

field	type	required	description
type	string	true	Must be “looker-add-dashboard-filter”.
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.

looker-conversational-analytics

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-conversational-analytics tool allows you to ask questions about your Looker data.

looker-conversational-analytics accepts two parameters:

user_query_with_context: The question asked of the Conversational Analytics system.
explore_references: A list of one to five explores that can be queried to answer the question. The form of the entry is [{"model": "model name", "explore": "explore name"}, ...]

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: ask_data_insights
type: looker-conversational-analytics
source: looker-source
description: |
 Use this tool to ask questions about your data using the Looker Conversational
 Analytics API. You must provide a natural language query and a list of
 1 to 5 model and explore combinations (e.g. [{'model': 'the_model', 'explore': 'the_explore'}]).
 Use the 'get_models' and 'get_explores' tools to discover available models and explores.

Reference

field	type	required	description
type	string	true	Must be “lookerca-conversational-analytics”.
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.

looker-create-project-directory

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-create-project-directory tool creates a new directory within a specified LookML project.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: looker-create-project-directory
type: looker-create-project-directory
source: looker-source
description: |
 This tool creates a new directory within a specific LookML project.
 It is useful for organizing project files.

 Parameters:
 - project_id (string): The ID of the LookML project.
 - directory_path (string): The path of the directory to create.

 Output:
 A string confirming the creation of the directory.

Reference

field	type	required	description
type	string	true	Must be “looker-create-project-directory”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-create-project-file

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-create-project-file tool creates a new LookML file in a project

looker-create-project-file accepts a project_id parameter and a file_path parameter as well as the file content.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: create_project_file
type: looker-create-project-file
source: looker-source
description: |
 This tool creates a new LookML file within a specified project, populating
 it with the provided content.

 Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first.

 Parameters:
 - project_id (required): The unique ID of the LookML project.
 - file_path (required): The desired path and filename for the new file within the project.
 - content (required): The full LookML content to write into the new file.

 Output:
 A confirmation message upon successful file creation.

Reference

field	type	required	description
type	string	true	Must be “looker-create-project-file”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-delete-project-directory

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-delete-project-directory tool deletes a directory from a specified LookML project.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: looker-delete-project-directory
type: looker-delete-project-directory
source: looker-source
description: |
 This tool deletes a directory from a specific LookML project.
 It is useful for removing unnecessary or obsolete directories.

 Parameters:
 - project_id (string): The ID of the LookML project.
 - directory_path (string): The path of the directory to delete.

 Output:
 A string confirming the deletion of the directory.

Reference

field	type	required	description
type	string	true	Must be “looker-delete-project-directory”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-delete-project-file

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-delete-project-file tool deletes a LookML file in a project

looker-delete-project-file accepts a project_id parameter and a file_path parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: delete_project_file
type: looker-delete-project-file
source: looker-source
description: |
 This tool permanently deletes a specified LookML file from within a project.
 Use with caution, as this action cannot be undone through the API.

 Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first.

 Parameters:
 - project_id (required): The unique ID of the LookML project.
 - file_path (required): The exact path to the LookML file to delete within the project.

 Output:
 A confirmation message upon successful file deletion.

Reference

field	type	required	description
type	string	true	Must be “looker-delete-project-file”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-dev-mode

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-dev-mode tool changes the session into and out of dev mode.

looker-dev-mode accepts a boolean parameter, true to enter dev mode and false to exit dev mode.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: dev_mode
type: looker-dev-mode
source: looker-source
description: |
 This tool allows toggling the Looker IDE session between Development Mode and Production Mode.
 Development Mode enables making and testing changes to LookML projects.

 Parameters:
 - enable (required): A boolean value.
 - `true`: Switches the current session to Development Mode.
 - `false`: Switches the current session to Production Mode.

Reference

field	type	required	description
type	string	true	Must be “looker-dev-mode”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-generate-embed-url

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-generate-embed-url tool generates an embeddable URL for a given piece of Looker content. The url generated is created for the user authenticated to the Looker source. When opened in the browser it will create a Looker Embed session.

looker-generate-embed-url takes two parameters:

the type of content (e.g., “dashboards”, “looks”, “query-visualization”)
the id of the content

It’s recommended to use other tools from the Looker MCP toolbox with this tool to do things like fetch dashboard id’s, generate a query, etc that can be supplied to this tool.

looker-get-connection-databases

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-connection-databases tool returns all the databases in a connection.

looker-get-connection-databases accepts a conn parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_connection_databases
type: looker-get-connection-databases
source: looker-source
description: |
 This tool retrieves a list of databases available through a specified Looker connection.
 This is only applicable for connections that support multiple databases.
 Use `get_connections` to check if a connection supports multiple databases.

 Parameters:
 - connection_name (required): The name of the database connection, obtained from `get_connections`.

 Output:
 A JSON array of strings, where each string is the name of an available database.
 If the connection does not support multiple databases, an empty list or an error will be returned.

Reference

field	type	required	description
type	string	true	Must be “looker-get-connection-databases”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-connection-schemas

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-connection-schemas tool returns all the schemas in a connection.

looker-get-connection-schemas accepts a conn parameter and an optional db parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_connection_schemas
type: looker-get-connection-schemas
source: looker-source
description: |
 This tool retrieves a list of database schemas available through a specified
 Looker connection.

 Parameters:
 - connection_name (required): The name of the database connection, obtained from `get_connections`.
 - database (optional): An optional database name to filter the schemas.
 Only applicable for connections that support multiple databases.

 Output:
 A JSON array of strings, where each string is the name of an available schema.

Reference

field	type	required	description
type	string	true	Must be “looker-get-connection-schemas”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-connection-table-columns

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-connection-table-columns tool returns all the columnes for each table specified.

looker-get-connection-table-columns accepts a conn parameter, a schema parameter, a tables parameter with a comma separated list of tables, and an optional db parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_connection_table_columns
type: looker-get-connection-table-columns
source: looker-source
description: |
 This tool retrieves a list of columns for one or more specified tables within a
 given database schema and connection.

 Parameters:
 - connection_name (required): The name of the database connection, obtained from `get_connections`.
 - schema (required): The name of the schema where the tables reside, obtained from `get_connection_schemas`.
 - tables (required): A comma-separated string of table names for which to retrieve columns
 (e.g., "users,orders,products"), obtained from `get_connection_tables`.
 - database (optional): The name of the database to filter by. Only applicable for connections
 that support multiple databases (check with `get_connections`).

 Output:
 A JSON array of objects, where each object represents a column and contains details
 such as `table_name`, `column_name`, `data_type`, and `is_nullable`.

Reference

field	type	required	description
type	string	true	Must be “looker-get-connection-table-columns”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-connection-tables

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-connection-tables tool returns all the tables in a connection.

looker-get-connection-tables accepts a conn parameter, a schema parameter, and an optional db parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_connection_tables
type: looker-get-connection-tables
source: looker-source
description: |
 This tool retrieves a list of tables available within a specified database schema
 through a Looker connection.

 Parameters:
 - connection_name (required): The name of the database connection, obtained from `get_connections`.
 - schema (required): The name of the schema to list tables from, obtained from `get_connection_schemas`.
 - database (optional): The name of the database to filter by. Only applicable for connections
 that support multiple databases (check with `get_connections`).

 Output:
 A JSON array of strings, where each string is the name of an available table.

Reference

field	type	required	description
type	string	true	Must be “looker-get-connection-tables”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-connections

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-connections tool returns all the connections in the source.

looker-get-connections accepts no parameters.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_connections
type: looker-get-connections
source: looker-source
description: |
 This tool retrieves a list of all database connections configured in the Looker system.

 Parameters:
 This tool takes no parameters.

 Output:
 A JSON array of objects, each representing a database connection and including details such as:
 - `name`: The connection's unique identifier.
 - `dialect`: The database dialect (e.g., "mysql", "postgresql", "bigquery").
 - `default_schema`: The default schema for the connection.
 - `database`: The associated database name (if applicable).
 - `supports_multiple_databases`: A boolean indicating if the connection can access multiple databases.

Reference

field	type	required	description
type	string	true	Must be “looker-get-connections”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-dashboards

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-get-dashboards tool searches for a saved Dashboard by name or description.

looker-get-dashboards takes four parameters, the title, desc, limit and offset.

Title and description use SQL style wildcards and are case insensitive.

Limit and offset are used to page through a larger set of matches and default to 100 and 0.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_dashboards
type: looker-get-dashboards
source: looker-source
description: |
 This tool searches for saved dashboards in a Looker instance. It returns a list of JSON objects, each representing a dashboard.

 Search Parameters:
 - title (optional): Filter by dashboard title (supports wildcards).
 - folder_id (optional): Filter by the ID of the folder where the dashboard is saved.
 - user_id (optional): Filter by the ID of the user who created the dashboard.
 - description (optional): Filter by description content (supports wildcards).
 - id (optional): Filter by specific dashboard ID.
 - limit (optional): Maximum number of results to return. Defaults to a system limit.
 - offset (optional): Starting point for pagination.

 String Search Behavior:
 - Case-insensitive matching.
 - Supports SQL LIKE pattern match wildcards:
 - `%`: Matches any sequence of zero or more characters. (e.g., `"finan%"` matches "financial", "finance")
 - `_`: Matches any single character. (e.g., `"s_les"` matches "sales")
 - Special expressions for null checks:
 - `"IS NULL"`: Matches dashboards where the field is null.
 - `"NOT NULL"`: Excludes dashboards where the field is null.

Reference

field	type	required	description
type	string	true	Must be “looker-get-dashboards”
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.

looker-get-dimensions

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-dimensions tool returns all the dimensions from a given explore in a given model in the source.

looker-get-dimensions accepts two parameters, the model and the explore.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_dimensions
type: looker-get-dimensions
source: looker-source
description: |
 This tool retrieves a list of dimensions defined within a specific Looker explore.
 Dimensions are non-aggregatable attributes or characteristics of your data
 (e.g., product name, order date, customer city) that can be used for grouping,
 filtering, or segmenting query results.

 Parameters:
 - model_name (required): The name of the LookML model, obtained from `get_models`.
 - explore_name (required): The name of the explore within the model, obtained from `get_explores`.

 Output Details:
 - If a dimension includes a `suggestions` field, its contents are valid values
 that can be used directly as filters for that dimension.
 - If a `suggest_explore` and `suggest_dimension` are provided, you can query
 that specified explore and dimension to retrieve a list of valid filter values.

The response is a json array with the following elements:

looker-get-explores

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-explores tool returns all explores for a given model from the source.

looker-get-explores accepts one parameter, the model id.

The return type is an array of maps, each map is formatted like:

{
 "name": "explore name",
 "description": "explore description",
 "label": "explore label",
 "group_label": "group label"
}

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_explores
type: looker-get-explores
source: looker-source
description: |
 This tool retrieves a list of explores defined within a specific LookML model.
 Explores represent a curated view of your data, typically joining several
 tables together to allow for focused analysis on a particular subject area.
 The output provides details like the explore's `name` and `label`.

 Parameters:
 - model_name (required): The name of the LookML model, obtained from `get_models`.

Reference

field	type	required	description
type	string	true	Must be “looker-get-explores”.
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.

looker-get-filters

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-filters tool returns all the filters from a given explore in a given model in the source.

looker-get-filters accepts two parameters, the model and the explore.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_filters
type: looker-get-filters
source: looker-source
description: |
 This tool retrieves a list of "filter-only fields" defined within a specific
 Looker explore. These are special fields defined in LookML specifically to
 create user-facing filter controls that do not directly affect the `GROUP BY`
 clause of the SQL query. They are often used in conjunction with liquid templating
 to create dynamic queries.

 Note: Regular dimensions and measures can also be used as filters in a query.
 This tool *only* returns fields explicitly defined as `filter:` in LookML.

 Parameters:
 - model_name (required): The name of the LookML model, obtained from `get_models`.
 - explore_name (required): The name of the explore within the model, obtained from `get_explores`.

The response is a json array with the following elements:

looker-get-looks

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-get-looks tool searches for a saved Look by name or description.

looker-get-looks takes four parameters, the title, desc, limit and offset.

Title and description use SQL style wildcards and are case insensitive.

Limit and offset are used to page through a larger set of matches and default to 100 and 0.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_looks
type: looker-get-looks
source: looker-source
description: |
 This tool searches for saved Looks (pre-defined queries and visualizations)
 in a Looker instance. It returns a list of JSON objects, each representing a Look.

 Search Parameters:
 - title (optional): Filter by Look title (supports wildcards).
 - folder_id (optional): Filter by the ID of the folder where the Look is saved.
 - user_id (optional): Filter by the ID of the user who created the Look.
 - description (optional): Filter by description content (supports wildcards).
 - id (optional): Filter by specific Look ID.
 - limit (optional): Maximum number of results to return. Defaults to a system limit.
 - offset (optional): Starting point for pagination.

 String Search Behavior:
 - Case-insensitive matching.
 - Supports SQL LIKE pattern match wildcards:
 - `%`: Matches any sequence of zero or more characters. (e.g., `"dan%"` matches "danger", "Danzig")
 - `_`: Matches any single character. (e.g., `"D_m%"` matches "Damage", "dump")
 - Special expressions for null checks:
 - `"IS NULL"`: Matches Looks where the field is null.
 - `"NOT NULL"`: Excludes Looks where the field is null.

Reference

field	type	required	description
type	string	true	Must be “looker-get-looks”
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.

looker-get-measures

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-measures tool returns all the measures from a given explore in a given model in the source.

looker-get-measures accepts two parameters, the model and the explore.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_measures
type: looker-get-measures
source: looker-source
description: |
 This tool retrieves a list of measures defined within a specific Looker explore.
 Measures are aggregatable metrics (e.g., total sales, average price, count of users)
 that are used for calculations and quantitative analysis in your queries.

 Parameters:
 - model_name (required): The name of the LookML model, obtained from `get_models`.
 - explore_name (required): The name of the explore within the model, obtained from `get_explores`.

 Output Details:
 - If a measure includes a `suggestions` field, its contents are valid values
 that can be used directly as filters for that measure.
 - If a `suggest_explore` and `suggest_dimension` are provided, you can query
 that specified explore and dimension to retrieve a list of valid filter values.

The response is a json array with the following elements:

looker-get-models

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-models tool returns all the models in the source.

looker-get-models accepts no parameters.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_models
type: looker-get-models
source: looker-source
description: |
 This tool retrieves a list of available LookML models in the Looker instance.
 LookML models define the data structure and relationships that users can query.
 The output includes details like the model's `name` and `label`, which are
 essential for subsequent calls to tools like `get_explores` or `query`.

 This tool takes no parameters.

Reference

field	type	required	description
type	string	true	Must be “looker-get-models”.
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.

looker-get-parameters

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-parameters tool returns all the parameters from a given explore in a given model in the source.

looker-get-parameters accepts two parameters, the model and the explore.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_parameters
type: looker-get-parameters
source: looker-source
description: |
 This tool retrieves a list of parameters defined within a specific Looker explore.
 LookML parameters are dynamic input fields that allow users to influence query
 behavior without directly modifying the underlying LookML. They are often used
 with `liquid` templating to create flexible dashboards and reports, enabling
 users to choose dimensions, measures, or other query components at runtime.

 Parameters:
 - model_name (required): The name of the LookML model, obtained from `get_models`.
 - explore_name (required): The name of the explore within the model, obtained from `get_explores`.

The response is a json array with the following elements:

looker-get-project-directories

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-project-directories tool retrieves the directories within a specified LookML project.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: looker-get-project-directories
type: looker-get-project-directories
source: looker-source
description: |
 This tool retrieves a list of directories within a specific LookML project.
 It is useful for exploring the project structure.

 Parameters:
 - project_id (string): The ID of the LookML project.

 Output:
 A JSON array of strings, representing the directories within the project.

Reference

field	type	required	description
type	string	true	Must be “looker-get-project-directories”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-project-file

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-project-file tool returns the contents of a LookML file.

looker-get-project-file accepts a project_id parameter and a file_path parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_project_file
type: looker-get-project-file
source: looker-source
description: |
 This tool retrieves the raw content of a specific LookML file from within a project.

 Parameters:
 - project_id (required): The unique ID of the LookML project, obtained from `get_projects`.
 - file_path (required): The path to the LookML file within the project,
 typically obtained from `get_project_files`.

 Output:
 The raw text content of the specified LookML file.

Reference

field	type	required	description
type	string	true	Must be “looker-get-project-file”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-project-files

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-project-files tool returns all the lookml files in a project in the source.

looker-get-project-files accepts a project_id parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_project_files
type: looker-get-project-files
source: looker-source
description: |
 This tool retrieves a list of all LookML files within a specified project,
 providing details about each file.

 Parameters:
 - project_id (required): The unique ID of the LookML project, obtained from `get_projects`.

 Output:
 A JSON array of objects, each representing a LookML file and containing
 details such as `path`, `id`, `type`, and `git_status`.

Reference

field	type	required	description
type	string	true	Must be “looker-get-project-files”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-get-projects

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-get-projects tool returns all the projects in the source.

looker-get-projects accepts no parameters.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: get_projects
type: looker-get-projects
source: looker-source
description: |
 This tool retrieves a list of all LookML projects available on the Looker instance.
 It is useful for identifying projects before performing actions like retrieving
 project files or making modifications.

 Parameters:
 This tool takes no parameters.

 Output:
 A JSON array of objects, each containing the `project_id` and `project_name`
 for a LookML project.

Reference

field	type	required	description
type	string	true	Must be “looker-get-projects”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-git-branch

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-git-branch tool is used to retrieve and manipulate the git branch of a LookML project.

looker-git-branch requires two parameters, the LookML project_id and the operation. The operation must be one of list, get, create, switch, or delete.

The list operation retrieves the list of available branches. The get operation retrieves the current branch.

create, switch and delete all require an additional parameter, the branch name. The create operation creates a new branch. The switch operation switches to the specified branch. The delete operation deletes the specified branch.

looker-health-analyze

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-health-analyze tool performs various analysis tasks on a Looker instance. The action parameter selects the type of analysis to perform:

projects: Analyzes all projects or a specified project, reporting on the number of models and view files, as well as Git connection and validation status.
models: Analyzes all models or a specified model, providing a count of explores, unused explores, and total query counts.
explores: Analyzes all explores or a specified explore, reporting on the number of joins, unused joins, fields, unused fields, and query counts. Being classified as Unused is determined by whether a field has been used as a field or filter within the past 90 days in production.

Compatible Sources

This tool can be used with the following database sources:

looker-health-pulse

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-health-pulse tool performs health checks on a Looker instance. The action parameter selects the type of check to perform:

check_db_connections: Checks all database connections, runs supported tests, and reports query counts.
check_dashboard_performance: Finds dashboards with slow running queries in the last 7 days.
check_dashboard_errors: Lists dashboards with erroring queries in the last 7 days.
check_explore_performance: Lists the slowest explores in the last 7 days and reports average query runtime.
check_schedule_failures: Lists schedules that have failed in the last 7 days.
check_legacy_features: Lists enabled legacy features. (To note, this function is not available in Looker Core.)

Compatible Sources

This tool can be used with the following database sources:

looker-health-vacuum

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-health-vacuum tool helps you identify unused LookML objects such as models, explores, joins, and fields. The action parameter selects the type of vacuum to perform:

models: Identifies unused explores within a model.
explores: Identifies unused joins and fields within an explore.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Parameters

field	type	required	description
action	string	true	The vacuum to perform: `models`, or `explores`.
project	string	false	The name of the Looker project to vacuum.
model	string	false	The name of the Looker model to vacuum.
explore	string	false	The name of the Looker explore to vacuum.
timeframe	int	false	The timeframe in days to analyze for usage. Defaults to 90.
min_queries	int	false	The minimum number of queries for an object to be considered used. Defaults to 1.

Example

Identify unnused fields (in this case, less than 1 query in the last 20 days) and joins in the order_items explore and thelook model

looker-make-dashboard

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-make-dashboard creates a dashboard in the user’s Looker personal folder.

looker-make-dashboard takes three parameters:

the title
the description
an optional folder id. If not provided, the user’s default folder will be used.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: make_dashboard
type: looker-make-dashboard
source: looker-source
description: |
 This tool creates a new, empty dashboard in Looker. Dashboards are stored
 in the user's personal folder, and the dashboard name must be unique.
 After creation, use `add_dashboard_filter` to add filters and
 `add_dashboard_element` to add content tiles.

 Required Parameters:
 - title (required): A unique title for the new dashboard.
 - description (required): A brief description of the dashboard's purpose.

 Output:
 A JSON object containing a link (`url`) to the newly created dashboard and
 its unique `id`. This `dashboard_id` is crucial for subsequent calls to
 `add_dashboard_filter` and `add_dashboard_element`.

Reference

field	type	required	description
type	string	true	Must be “looker-make-dashboard”
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.

looker-make-look

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-make-look creates a saved Look in the user’s Looker personal folder.

looker-make-look takes twelve 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
an optional vis_config
the title
an optional description
an optional folder id. If not provided, the user’s default folder will be used.

Compatible Sources

This tool can be used with the following database sources:

looker-query

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-query tool runs a query using the Looker semantic model.

looker-query 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.

looker-query-sql

Mon, 01 Jan 0001 00:00:00 +0000

About

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

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.

looker-query-url

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-query-url generates a url link to an explore in Looker so the query can be investigated further.

looker-query-url takes nine 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
an optional vis_config

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: query_url
type: looker-query-url
source: looker-source
description: |
 This tool generates a shareable URL for a Looker query, allowing users to
 explore the query further within the Looker UI. It returns the generated URL,
 along with the `query_id` and `slug`.

 Parameters:
 All query parameters (e.g., `model_name`, `explore_name`, `fields`, `pivots`,
 `filters`, `sorts`, `limit`, `query_timezone`) are the same as the `query` tool.

 Additionally, it accepts an optional `vis_config` parameter:
 - vis_config (optional): A JSON object that controls the default visualization
 settings for the generated query.

 vis_config Details:
 The `vis_config` object supports a wide range of properties for various chart types.
 Here are some notes on making visualizations.

 ### Cartesian Charts (Area, Bar, Column, Line, Scatter)

 These chart types share a large number of configuration options.

 **General**
 * `type`: The type of visualization (`looker_area`, `looker_bar`, `looker_column`, `looker_line`, `looker_scatter`).
 * `series_types`: Override the chart type for individual series.
 * `show_view_names`: Display view names in labels and tooltips (`true`/`false`).
 * `series_labels`: Provide custom names for series.

 **Styling & Colors**
 * `colors`: An array of color values to be used for the chart series.
 * `series_colors`: A mapping of series names to specific color values.
 * `color_application`: Advanced controls for color palette application (collection, palette, reverse, etc.).
 * `font_size`: Font size for labels (e.g., '12px').

 **Legend**
 * `hide_legend`: Show or hide the chart legend (`true`/`false`).
 * `legend_position`: Placement of the legend (`'center'`, `'left'`, `'right'`).

 **Axes**
 * `swap_axes`: Swap the X and Y axes (`true`/`false`).
 * `x_axis_scale`: Scale of the x-axis (`'auto'`, `'ordinal'`, `'linear'`, `'time'`).
 * `x_axis_reversed`, `y_axis_reversed`: Reverse the direction of an axis (`true`/`false`).
 * `x_axis_gridlines`, `y_axis_gridlines`: Display gridlines for an axis (`true`/`false`).
 * `show_x_axis_label`, `show_y_axis_label`: Show or hide the axis title (`true`/`false`).
 * `show_x_axis_ticks`, `show_y_axis_ticks`: Show or hide axis tick marks (`true`/`false`).
 * `x_axis_label`, `y_axis_label`: Set a custom title for an axis.
 * `x_axis_datetime_label`: A format string for datetime labels on the x-axis (e.g., `'%Y-%m'`).
 * `x_padding_left`, `x_padding_right`: Adjust padding on the ends of the x-axis.
 * `x_axis_label_rotation`, `x_axis_label_rotation_bar`: Set rotation for x-axis labels.
 * `x_axis_zoom`, `y_axis_zoom`: Enable zooming on an axis (`true`/`false`).
 * `y_axes`: An array of configuration objects for multiple y-axes.

 **Data & Series**
 * `stacking`: How to stack series (`''` for none, `'normal'`, `'percent'`).
 * `ordering`: Order of series in a stack (`'none'`, etc.).
 * `limit_displayed_rows`: Enable or disable limiting the number of rows displayed (`true`/`false`).
 * `limit_displayed_rows_values`: Configuration for the row limit (e.g., `{ "first_last": "first", "show_hide": "show", "num_rows": 10 }`).
 * `discontinuous_nulls`: How to render null values in line charts (`true`/`false`).
 * `point_style`: Style for points on line and area charts (`'none'`, `'circle'`, `'circle_outline'`).
 * `series_point_styles`: Override point styles for individual series.
 * `interpolation`: Line interpolation style (`'linear'`, `'monotone'`, `'step'`, etc.).
 * `show_value_labels`: Display values on data points (`true`/`false`).
 * `label_value_format`: A format string for value labels.
 * `show_totals_labels`: Display total labels on stacked charts (`true`/`false`).
 * `totals_color`: Color for total labels.
 * `show_silhouette`: Display a "silhouette" of hidden series in stacked charts (`true`/`false`).
 * `hidden_series`: An array of series names to hide from the visualization.

 **Scatter/Bubble Specific**
 * `size_by_field`: The field used to determine the size of bubbles.
 * `color_by_field`: The field used to determine the color of bubbles.
 * `plot_size_by_field`: Whether to display the size-by field in the legend.
 * `cluster_points`: Group nearby points into clusters (`true`/`false`).
 * `quadrants_enabled`: Display quadrants on the chart (`true`/`false`).
 * `quadrant_properties`: Configuration for quadrant labels and colors.
 * `custom_quadrant_value_x`, `custom_quadrant_value_y`: Set quadrant boundaries as a percentage.
 * `custom_quadrant_point_x`, `custom_quadrant_point_y`: Set quadrant boundaries to a specific value.

 **Miscellaneous**
 * `reference_lines`: Configuration for displaying reference lines.
 * `trend_lines`: Configuration for displaying trend lines.
 * `trellis`: Configuration for creating trellis (small multiple) charts.
 * `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering interactions.

 ### Boxplot

 * Inherits most of the Cartesian chart options.
 * `type`: Must be `looker_boxplot`.

 ### Funnel

 * `type`: Must be `looker_funnel`.
 * `orientation`: How data is read (`'automatic'`, `'dataInRows'`, `'dataInColumns'`).
 * `percentType`: How percentages are calculated (`'percentOfMaxValue'`, `'percentOfPriorRow'`).
 * `labelPosition`, `valuePosition`, `percentPosition`: Placement of labels (`'left'`, `'right'`, `'inline'`, `'hidden'`).
 * `labelColor`, `labelColorEnabled`: Set a custom color for labels.
 * `labelOverlap`: Allow labels to overlap (`true`/`false`).
 * `barColors`: An array of colors for the funnel steps.
 * `color_application`: Advanced color palette controls.
 * `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering.

 ### Pie / Donut

 * `type`: Must be `looker_pie`.
 * `value_labels`: Where to display values (`'legend'`, `'labels'`).
 * `label_type`: The format of data labels (`'labPer'`, `'labVal'`, `'lab'`, `'val'`, `'per'`).
 * `start_angle`, `end_angle`: The start and end angles of the pie chart.
 * `inner_radius`: The inner radius, used to create a donut chart.
 * `series_colors`, `series_labels`: Override colors and labels for specific slices.
 * `color_application`: Advanced color palette controls.
 * `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering.
 * `advanced_vis_config`: A string containing JSON for advanced Highcharts configuration.

 ### Waterfall

 * Inherits most of the Cartesian chart options.
 * `type`: Must be `looker_waterfall`.
 * `up_color`: Color for positive (increasing) values.
 * `down_color`: Color for negative (decreasing) values.
 * `total_color`: Color for the total bar.

 ### Word Cloud

 * `type`: Must be `looker_wordcloud`.
 * `rotation`: Enable random word rotation (`true`/`false`).
 * `colors`: An array of colors for the words.
 * `color_application`: Advanced color palette controls.
 * `crossfilterEnabled`, `crossfilters`: Configuration for cross-filtering.

 These are some sample vis_config settings.

 A bar chart -
 {{
 "defaults_version": 1,
 "label_density": 25,
 "legend_position": "center",
 "limit_displayed_rows": false,
 "ordering": "none",
 "plot_size_by_field": false,
 "point_style": "none",
 "show_null_labels": false,
 "show_silhouette": false,
 "show_totals_labels": false,
 "show_value_labels": false,
 "show_view_names": false,
 "show_x_axis_label": true,
 "show_x_axis_ticks": true,
 "show_y_axis_labels": true,
 "show_y_axis_ticks": true,
 "stacking": "normal",
 "totals_color": "#808080",
 "trellis": "",
 "type": "looker_bar",
 "x_axis_gridlines": false,
 "x_axis_reversed": false,
 "x_axis_scale": "auto",
 "x_axis_zoom": true,
 "y_axis_combined": true,
 "y_axis_gridlines": true,
 "y_axis_reversed": false,
 "y_axis_scale_mode": "linear",
 "y_axis_tick_density": "default",
 "y_axis_tick_density_custom": 5,
 "y_axis_zoom": true
 }}

 A column chart with an option advanced_vis_config -
 {{
 "advanced_vis_config": "{ chart: { type: 'pie', spacingBottom: 50, spacingLeft: 50, spacingRight: 50, spacingTop: 50, }, legend: { enabled: false, }, plotOptions: { pie: { dataLabels: { enabled: true, format: '\u003cb\u003e{key}\u003c/b\u003e\u003cspan style=\"font-weight: normal\"\u003e - {percentage:.2f}%\u003c/span\u003e', }, showInLegend: false, }, }, series: [], }",
 "colors": [
 "grey"
 ],
 "defaults_version": 1,
 "hidden_fields": [],
 "label_density": 25,
 "legend_position": "center",
 "limit_displayed_rows": false,
 "note_display": "below",
 "note_state": "collapsed",
 "note_text": "Unsold inventory only",
 "ordering": "none",
 "plot_size_by_field": false,
 "point_style": "none",
 "series_colors": {},
 "show_null_labels": false,
 "show_silhouette": false,
 "show_totals_labels": false,
 "show_value_labels": true,
 "show_view_names": false,
 "show_x_axis_label": true,
 "show_x_axis_ticks": true,
 "show_y_axis_labels": true,
 "show_y_axis_ticks": true,
 "stacking": "normal",
 "totals_color": "#808080",
 "trellis": "",
 "type": "looker_column",
 "x_axis_gridlines": false,
 "x_axis_reversed": false,
 "x_axis_scale": "auto",
 "x_axis_zoom": true,
 "y_axes": [],
 "y_axis_combined": true,
 "y_axis_gridlines": true,
 "y_axis_reversed": false,
 "y_axis_scale_mode": "linear",
 "y_axis_tick_density": "default",
 "y_axis_tick_density_custom": 5,
 "y_axis_zoom": true
 }}

 A line chart -
 {{
 "defaults_version": 1,
 "hidden_pivots": {},
 "hidden_series": [],
 "interpolation": "linear",
 "label_density": 25,
 "legend_position": "center",
 "limit_displayed_rows": false,
 "plot_size_by_field": false,
 "point_style": "none",
 "series_types": {},
 "show_null_points": true,
 "show_value_labels": false,
 "show_view_names": false,
 "show_x_axis_label": true,
 "show_x_axis_ticks": true,
 "show_y_axis_labels": true,
 "show_y_axis_ticks": true,
 "stacking": "",
 "trellis": "",
 "type": "looker_line",
 "x_axis_gridlines": false,
 "x_axis_reversed": false,
 "x_axis_scale": "auto",
 "y_axis_combined": true,
 "y_axis_gridlines": true,
 "y_axis_reversed": false,
 "y_axis_scale_mode": "linear",
 "y_axis_tick_density": "default",
 "y_axis_tick_density_custom": 5
 }}

 An area chart -
 {{
 "defaults_version": 1,
 "interpolation": "linear",
 "label_density": 25,
 "legend_position": "center",
 "limit_displayed_rows": false,
 "plot_size_by_field": false,
 "point_style": "none",
 "series_types": {},
 "show_null_points": true,
 "show_silhouette": false,
 "show_totals_labels": false,
 "show_value_labels": false,
 "show_view_names": false,
 "show_x_axis_label": true,
 "show_x_axis_ticks": true,
 "show_y_axis_labels": true,
 "show_y_axis_ticks": true,
 "stacking": "normal",
 "totals_color": "#808080",
 "trellis": "",
 "type": "looker_area",
 "x_axis_gridlines": false,
 "x_axis_reversed": false,
 "x_axis_scale": "auto",
 "x_axis_zoom": true,
 "y_axis_combined": true,
 "y_axis_gridlines": true,
 "y_axis_reversed": false,
 "y_axis_scale_mode": "linear",
 "y_axis_tick_density": "default",
 "y_axis_tick_density_custom": 5,
 "y_axis_zoom": true
 }}

 A scatter plot -
 {{
 "cluster_points": false,
 "custom_quadrant_point_x": 5,
 "custom_quadrant_point_y": 5,
 "custom_value_label_column": "",
 "custom_x_column": "",
 "custom_y_column": "",
 "defaults_version": 1,
 "hidden_fields": [],
 "hidden_pivots": {},
 "hidden_points_if_no": [],
 "hidden_series": [],
 "interpolation": "linear",
 "label_density": 25,
 "legend_position": "center",
 "limit_displayed_rows": false,
 "limit_displayed_rows_values": {
 "first_last": "first",
 "num_rows": 0,
 "show_hide": "hide"
 },
 "plot_size_by_field": false,
 "point_style": "circle",
 "quadrant_properties": {
 "0": {
 "color": "",
 "label": "Quadrant 1"
 },
 "1": {
 "color": "",
 "label": "Quadrant 2"
 },
 "2": {
 "color": "",
 "label": "Quadrant 3"
 },
 "3": {
 "color": "",
 "label": "Quadrant 4"
 }
 },
 "quadrants_enabled": false,
 "series_labels": {},
 "series_types": {},
 "show_null_points": false,
 "show_value_labels": false,
 "show_view_names": true,
 "show_x_axis_label": true,
 "show_x_axis_ticks": true,
 "show_y_axis_labels": true,
 "show_y_axis_ticks": true,
 "size_by_field": "roi",
 "stacking": "normal",
 "swap_axes": true,
 "trellis": "",
 "type": "looker_scatter",
 "x_axis_gridlines": false,
 "x_axis_reversed": false,
 "x_axis_scale": "auto",
 "x_axis_zoom": true,
 "y_axes": [
 {
 "label": "",
 "orientation": "bottom",
 "series": [
 {
 "axisId": "Channel_0 - average_of_roi_first",
 "id": "Channel_0 - average_of_roi_first",
 "name": "Channel_0"
 },
 {
 "axisId": "Channel_1 - average_of_roi_first",
 "id": "Channel_1 - average_of_roi_first",
 "name": "Channel_1"
 },
 {
 "axisId": "Channel_2 - average_of_roi_first",
 "id": "Channel_2 - average_of_roi_first",
 "name": "Channel_2"
 },
 {
 "axisId": "Channel_3 - average_of_roi_first",
 "id": "Channel_3 - average_of_roi_first",
 "name": "Channel_3"
 },
 {
 "axisId": "Channel_4 - average_of_roi_first",
 "id": "Channel_4 - average_of_roi_first",
 "name": "Channel_4"
 }
 ],
 "showLabels": true,
 "showValues": true,
 "tickDensity": "custom",
 "tickDensityCustom": 100,
 "type": "linear",
 "unpinAxis": false
 }
 ],
 "y_axis_combined": true,
 "y_axis_gridlines": true,
 "y_axis_reversed": false,
 "y_axis_scale_mode": "linear",
 "y_axis_tick_density": "default",
 "y_axis_tick_density_custom": 5,
 "y_axis_zoom": true
 }}

 A single record visualization -
 {{
 "defaults_version": 1,
 "show_view_names": false,
 "type": "looker_single_record"
 }}

 A single value visualization -
 {{
 "comparison_reverse_colors": false,
 "comparison_type": "value", "conditional_formatting_include_nulls": false, "conditional_formatting_include_totals": false,
 "custom_color": "#1A73E8",
 "custom_color_enabled": true,
 "defaults_version": 1,
 "enable_conditional_formatting": false,
 "series_types": {},
 "show_comparison": false,
 "show_comparison_label": true,
 "show_single_value_title": true,
 "single_value_title": "Total Clicks",
 "type": "single_value"
 }}

 A Pie chart -
 {{
 "defaults_version": 1,
 "label_density": 25,
 "label_type": "labPer",
 "legend_position": "center",
 "limit_displayed_rows": false,
 "ordering": "none",
 "plot_size_by_field": false,
 "point_style": "none",
 "series_types": {},
 "show_null_labels": false,
 "show_silhouette": false,
 "show_totals_labels": false,
 "show_value_labels": false,
 "show_view_names": false,
 "show_x_axis_label": true,
 "show_x_axis_ticks": true,
 "show_y_axis_labels": true,
 "show_y_axis_ticks": true,
 "stacking": "",
 "totals_color": "#808080",
 "trellis": "",
 "type": "looker_pie",
 "value_labels": "legend",
 "x_axis_gridlines": false,
 "x_axis_reversed": false,
 "x_axis_scale": "auto",
 "y_axis_combined": true,
 "y_axis_gridlines": true,
 "y_axis_reversed": false,
 "y_axis_scale_mode": "linear",
 "y_axis_tick_density": "default",
 "y_axis_tick_density_custom": 5
 }}

 The result is a JSON object with the id, slug, the url, and
 the long_url.

Reference

field	type	required	description
type	string	true	Must be “looker-query-url”
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.

looker-run-dashboard

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-run-dashboard tool runs the queries associated with a dashboard.

looker-run-dashboard takes one parameter, the dashboard_id.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: run_dashboard
type: looker-run-dashboard
source: looker-source
description: |
 This tool executes the queries associated with each tile in a specified dashboard
 and returns the aggregated data in a JSON structure.

 Parameters:
 - dashboard_id (required): The unique identifier of the dashboard to run,
 typically obtained from the `get_dashboards` tool.

 Output:
 The data from all dashboard tiles is returned as a JSON object.

Reference

field	type	required	description
type	string	true	Must be “looker-run-dashboard”
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.

looker-run-look

Mon, 01 Jan 0001 00:00:00 +0000

About

The looker-run-look tool runs the query associated with a saved Look.

looker-run-look takes one parameter, the look_id.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: run_look
type: looker-run-look
source: looker-source
description: |
 This tool executes the query associated with a saved Look and
 returns the resulting data in a JSON structure.

 Parameters:
 - look_id (required): The unique identifier of the Look to run,
 typically obtained from the `get_looks` tool.

 Output:
 The query results are returned as a JSON object.

Reference

field	type	required	description
type	string	true	Must be “looker-run-look”
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.

looker-update-project-file

Mon, 01 Jan 0001 00:00:00 +0000

About

A looker-update-project-file tool updates the content of a LookML file.

looker-update-project-file accepts a project_id parameter and a file_path parameter as well as the new file content.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

kind: tool
name: update_project_file
type: looker-update-project-file
source: looker-source
description: |
 This tool modifies the content of an existing LookML file within a specified project.

 Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first.

 Parameters:
 - project_id (required): The unique ID of the LookML project.
 - file_path (required): The exact path to the LookML file to modify within the project.
 - content (required): The new, complete LookML content to overwrite the existing file.

 Output:
 A confirmation message upon successful file modification.

Reference

field	type	required	description
type	string	true	Must be “looker-update-project-file”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.

looker-validate-project

Mon, 01 Jan 0001 00:00:00 +0000

About

A “looker-validate-project” tool checks the syntax of a LookML project and reports any errors

looker-validate-project accepts a project_id parameter.

Compatible Sources

This tool can be used with the following database sources:

Source Name
Looker

Example

tools:
 validate_project:
 kind: looker-validate-project
 source: looker-source
 description: |
 This tool checks a LookML project for syntax errors.

 Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` first.

 Parameters:
 - project_id (required): The unique ID of the LookML project.

 Output:
 A list of error details including the file path and line number, and also a list of models
 that are not currently valid due to LookML errors.

Reference

field	type	required	description
kind	string	true	Must be “looker-validate-project”.
source	string	true	Name of the source Looker instance.
description	string	true	Description of the tool that is passed to the LLM.