Get context
get_contextGet what the team wants AI tools to know about one connection: notes for AI (for example which table to prefer or what unit amounts are in), business definitions such as "active customer" with their SQL, and the description and synonyms of each described table and column. Call it once at the start of a conversation about a connection, after list_connections and before writing SQL, and follow the notes. Pass intent to get only the tables and definitions relevant to the question, which keeps the answer short on large databases. Descriptions written in SaturnSQL take the place of the database's own comments. Read-only. Refused on an approved_queries connection.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"connectionId": "<connectionId>"
},
"name": "get_context"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | No | The user's question or goal in a few words, e.g. "revenue by customer last month". Omit for everything that has context. | |
| connectionId | Yes | Connection id from list_connections. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| engine | No | ||
| tables | No | ||
| definitions | No | ||
| description | No | ||
| connectionId | No | ||
| instructions | No | Notes for AI from the team. Follow them. | |
| omittedTables | No | Described tables left out because they did not match intent. | |
| connectionName | No |