Skip to main content
Glama

Delete policy

delete_policy
Destructive

Delete a policy by its id from get_guard. 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": {
      "id": "<id>"
    },
    "name": "delete_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds prerequisites (admin role, write scope, SaturnSQL approval), the exact failure code GUARD_APPROVAL_REQUIRED, the approval/retry loop, expiry semantics, and the audit-trail behavior with the user's name. That is substantial context beyond the structured fields; only the return shape of a successful delete is left implicit.

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

Conciseness3/5

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

Front-loaded with the action and free of filler, but it packs permission checks, an error code, a multi-step approval workflow, expiry, and audit logging into one dense run-on paragraph; a short ordered list would make the retry sequence easier to execute reliably.

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, approval-gated mutation with no output schema, the definition covers who can call it, what blocks it, how to unblock, how long the approval lasts, how to close the session, and that changes are attributable to the user — nothing an agent needs in order to call it safely is missing.

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?

Schema coverage is 0% and the single 'id' parameter is an untyped-in-practice string, so the description carries the burden; it usefully tells the agent the id comes from get_guard, which the schema does not. It stops short of format details, but that is the only meaningful parameter here.

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?

States a specific verb and resource ('Delete a policy by its id') and anchors the id's origin to the sibling get_guard, so an agent can distinguish this from save_policy or the other delete_* tools without opening a schema.

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?

Explicitly narrows usage ('change it only when the user asked for this exact change, and say what will change first') and hands off the follow-up path to request_guard_edit and end_guard_edit, including the 12-hour approval window and the retry condition.

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