Skip to main content
Glama

Save policy

save_policy
Destructive

Create a plain-language policy for AI queries, such as "salaries only in aggregate", or replace one (pass id from get_guard). connectionId null applies it to every connection; action is block or ask_admin. Guard decides what AI tools, including you, may do on the team's databases, so change it only when the user asked for this exact change, and say what will change first. Needs an admin, the write scope, and an admin's approval in SaturnSQL for this AI tool: without it the call fails with code GUARD_APPROVAL_REQUIRED. Then call request_guard_edit, show the user the approvalUrl, and repeat the call after they approve. An approval lasts 12 hours; call end_guard_edit when the user's changes are done. Every change is recorded in SaturnSQL with the user's name.

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": {
      "text": "<text>"
    },
    "name": "save_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
textYes
actionNo
enabledNo
connectionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations declaring a destructive, non-read-only operation, it discloses admin and write-scope prerequisites, the GUARD_APPROVAL_REQUIRED failure mode, the approvalUrl flow, 12-hour expiry, and that every change is audited with the user's name. These are exactly the behavioral traits an agent needs before invoking a destructive mutation.

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

Conciseness4/5

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

It is front-loaded with the action and replacement path, then moves through constraints and approval workflow. The sentences are dense but carry necessary operational information; the long approval paragraph is justified by the complexity, though it could be broken up for scanability.

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

Completeness5/5

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

For a destructive policy mutation with no output schema and multiple preconditions, the description covers the approval flow, error code, duration, and cleanup via end_guard_edit. The only gap is the enabled parameter, which is minor relative to the operational detail provided.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates for most parameters: text example, id from get_guard for replacement, connectionId null meaning all connections, and action values block/ask_admin. The enabled parameter is never explained, leaving one of five parameters undocumented.

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

Purpose5/5

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

Opens with a specific verb and resource ("Create a plain-language policy for AI queries") and explicitly covers the replace path via an id from get_guard. It names the sibling tool get_guard, letting the agent distinguish this from reading or listing policies.

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

Usage Guidelines5/5

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

States precise usage constraints: change the guard only when the user asked for this exact change, and say what will change first. It also gives the replace path and the full approval workflow with request_guard_edit and end_guard_edit, including the 12-hour approval lifetime.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources