SaturnSQL

Save query

save_query

Destructive

Save a new query to the team's library, or update an existing one by passing its id.

Input Schema

Name	Required	Description
`id`	No	Id of the saved query to overwrite. Omit to create a new one.
`sql`	Yes	The SQL to save.
`name`	Yes	Display name in the query library.
`folderPath`	No	Single folder label to file it under; null or omitted for the root.
`connectionId`	No	Connection id from list_connections.

Output Schema

Name	Required	Description
`id`	No
`sql`	No
`name`	No
`isShared`	No
`updatedAt`	No
`variables`	No	Declared {{name}} variables, filled in by run_saved_query.
`folderPath`	No
`connectionId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / variables / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "type": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 9, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered externally. The description adds useful context that the query is saved to a team library and that an existing query is updated by id, but it does not explain overwrite impact, permissions, or side effects in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no waste. It efficiently communicates the core create-or-update behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a rich schema, full parameter descriptions, annotations, and an output schema, so the description need not restate return values or parameter details. It adequately explains the create/update duality, though it could say more about destructive overwrite behavior beyond what annotations provide.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters are already documented in the schema. The description only echoes the id-based update behavior and adds little parameter meaning beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: save a query to the team's library, including both create and update modes. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as list_queries or run_saved_query.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a useful internal rule: omit id to create, pass id to update. It does not explain when to use this tool instead of adjacent tools like run_saved_query or list_queries, so the usage guidance is implied rather than complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SaturnSQL tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?