Skip to main content
Glama

pmg_ruledb_rule_from_detach

Detach a 'from' (sender) group from a PMG RuleDB rule. Dry-run by default; use confirm=True to execute the removal.

Instructions

MUTATION (MEDIUM): detach a 'from' (sender/who) group from a PMG RuleDB rule. Dry-run by default.

Only removes the binding — the who-group itself is untouched (delete it separately with pmg_who_group_delete if desired). List current bindings with pmg_ruledb_rule_from_list. confirm=True executes and returns {"status": "ok", "result": <PMG's raw API response>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_YesRule ID to detach the group from.
ogroupYesNumeric 'who' group ID currently attached as the 'from' condition to detach.
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It clearly identifies the tool as a mutation, notes the dry-run default, explains that only the binding is removed and the group is untouched, and describes the effect of confirm=True. This is comprehensive but lacks mention of error handling or what happens if the rule or group does not exist.

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 concise, with each sentence serving a purpose: action declaration, dry-run hint, side effects, related tools, and confirm behavior. No superfluous words, and the structure is logical and front-loaded with the essential operation.

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?

Given the tool's narrow scope and the existence of an output schema (not shown but indicated), the description covers key aspects: operation, dry-run, side effects, and related tools. It does not explain the output format, but that is handled by the output schema. It is sufficient for an agent to use correctly.

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?

With 100% schema description coverage, the baseline is 3. The description adds only minor context about confirm=True and its effect, which is already in the schema. It does not elaborate on id_ or ogroup beyond the schema, so it adds limited additional meaning.

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?

The description clearly states it detaches a 'from' group from a PMG RuleDB rule, with explicit mention of it being a mutation and dry-run by default. It distinguishes from related tools like pmg_ruledb_rule_from_attach and pmg_ruledb_rule_from_list, and indicates the group itself is not deleted, providing a specific verb and resource.

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?

The description explicitly explains when to use the tool (to detach a binding), what it does not do (does not delete the who-group), and provides alternatives for listing bindings (pmg_ruledb_rule_from_list) and deleting the group (pmg_who_group_delete). It also explains the dry-run default and confirm behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server