chore: fix links (#1914)

Fixed broken links.

---------

Co-authored-by: Twisha Bansal <58483338+twishabansal@users.noreply.github.com>
This commit is contained in:
manuka rahul
2025-11-14 11:16:47 +05:30
committed by GitHub
parent 5156db2621
commit c858c49fd3
3 changed files with 7 additions and 7 deletions

View File

@@ -287,7 +287,7 @@ Your AI tool is now connected to Looker using MCP. Try asking your AI
assistant to list models, explores, dimensions, and measures. Run a
query, retrieve the SQL for a query, and run a saved Look.
The full tool list is available in the [Prebuilt Tools Reference](../../reference/prebuilt-tools/#looker).
The full tool list is available in the [Prebuilt Tools Reference](../../reference/prebuilt-tools.md/#looker).
The following tools are available to the LLM:

View File

@@ -14,7 +14,7 @@ aliases:
A `mindsdb-execute-sql` tool executes a SQL statement against a MindsDB
federated database. It's compatible with any of the following sources:
- [mindsdb](../sources/mindsdb.md)
- [mindsdb](../../sources/mindsdb.md)
`mindsdb-execute-sql` takes one input parameter `sql` and runs the SQL
statement against the `source`. This tool enables you to:
@@ -123,4 +123,4 @@ tools:
|-------------|:------------------------------------------:|:------------:|--------------------------------------------------------------------------------------------------|
| kind | string | true | Must be "mindsdb-execute-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. |
| description | string | true | Description of the tool that is passed to the LLM. |

View File

@@ -14,7 +14,7 @@ aliases:
A `mindsdb-sql` tool executes a pre-defined SQL statement against a MindsDB
federated database. It's compatible with any of the following sources:
- [mindsdb](../sources/mindsdb.md)
- [mindsdb](../../sources/mindsdb.md)
The specified SQL statement is executed as a [prepared statement][mysql-prepare],
and expects parameters in the SQL query to be in the form of placeholders `?`.
@@ -135,7 +135,7 @@ tools:
> including identifiers, column names, and table names. **This makes it more
> vulnerable to SQL injections**. Using basic parameters only (see above) is
> recommended for performance and safety reasons. For more details, please check
> [templateParameters](_index#template-parameters).
> [templateParameters](../#template-parameters).
```yaml
tools:
@@ -164,5 +164,5 @@ tools:
| 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. |
| statement | string | true | SQL statement to execute on. |
| parameters | [parameters](_index#specifying-parameters) | false | List of [parameters](_index#specifying-parameters) that will be inserted into the SQL statement. |
| templateParameters | [templateParameters](_index#template-parameters) | false | List of [templateParameters](_index#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |
| parameters | [parameters](../#specifying-parameters) | false | List of [parameters](../#specifying-parameters) that will be inserted into the SQL statement. |
| templateParameters | [templateParameters](../#template-parameters) | false | List of [templateParameters](../#template-parameters) that will be inserted into the SQL statement before executing prepared statement. |