Skip to main content
Glama

Save group

save_group
Destructive

Create a group of people for access rules, or rename one (pass 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": {
      "name": "<name>"
    },
    "name": "save_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
nameYes

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?

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes well beyond them: required privileges, the failure mode and literal error code GUARD_APPROVAL_REQUIRED, the approval round-trip via request_guard_edit plus approvalUrl, the 12-hour approval lifetime, and that every change is audited under the user's name. This is exactly the extra behavioral context the annotations cannot carry.

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?

Front-loaded with the dual-mode purpose before the approval workflow, and every sentence carries operational information rather than filler. It is on the long side, but the length is driven by a genuinely multi-step approval procedure rather than redundancy.

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 description covers prerequisites, the failure and recovery path, the sibling calls needed, and the expiration of the approval. An agent has everything needed to invoke it correctly and handle the failure case.

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%, so the description must explain the two parameters, and it does the important part: supplying id (from get_guard) switches the tool to rename, while omitting it creates a group, and name is what gets created/renamed. It does not mention the 1-100 character limit on name, but that constraint is visible in the schema.

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 ('Create a group of people for access rules') and covers the second mode ('or rename one') with the exact trigger for it ('pass id from get_guard'). An agent can tell the create path from the rename path and knows where the id comes from, so it is distinguishable from delete_group and set_group_member by verb and object.

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?

Gives explicit when-to-use guidance ('only when the user asked for this exact change, and say what will change first') and names the exact follow-up siblings: request_guard_edit before approval, repeat the call after, and end_guard_edit when the user's changes are done. It also states the prerequisite condition (admin, write scope, admin approval) that must hold before calling.

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