Skip to main content
Glama

LexQ

by io.lexq.mcp
OverviewDiscussionsAdmin

Create Policy Group

lexq_groups_create

Create a new policy group. Requires name. Priority is auto-assigned (appended last, tenant-wide); use lexq_groups_reorder to change order. Optionally set conflict resolution, activation group, and description. Policy groups that share an activationGroup form a cluster and must share the same activationMode / activationStrategy / executionLimit; executionLimit is how many of those groups run, not how many rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGroup name (unique among non-ARCHIVED)
descriptionNoGroup description
activationModeNoConflict resolution mode
executionLimitNoHow many policy groups sharing this activationGroup may run (required when mode is MAX_N). Counts groups, not rules: every rule of a winning group runs.
activationGroupNoActivation group (Execution Group) cluster key. Policy groups sharing this key compete, and group priority picks the winners.
activationStrategyNoRanking used to pick the winning groups when mode is EXCLUSIVE or MAX_N

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / activationGroup / description
      Previous value: -"Activation group name"New value: +"Activation group (Execution Group) cluster key. Policy groups sharing this key compete, and group priority picks the winners."
    • changedInput schema / properties / activationStrategy / description
      Previous value: -"Strategy when mode is EXCLUSIVE or MAX_N"New value: +"Ranking used to pick the winning groups when mode is EXCLUSIVE or MAX_N"
    • changedInput schema / properties / activationStrategy / enum
      Previous value: -[
-  "FIRST_MATCH",
-  "HIGHEST_PRIORITY",
-  "MAX_BENEFIT"
-]New value: +[
+  "HIGHEST_PRIORITY"
+]
    • changedInput schema / properties / executionLimit / description
      Previous value: -"Max rule executions (required when mode is MAX_N)"New value: +"How many policy groups sharing this activationGroup may run (required when mode is MAX_N). Counts groups, not rules: every rule of a winning group runs."
    • addedInput schema / properties / executionLimit / maximum
      Added value: +9007199254740991
  2. Changed2 schema fields changed
    • removedInput schema / properties / priority
      Removed value: -{
-  "description": "Execution priority (lower = higher)",
-  "minimum": 0,
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "priority"
-]New value: +[
+  "name"
+]
  3. Changed8 schema fields changed
    • addedInput schema / properties / activationGroup
      Added value: +{
+  "description": "Activation group name",
+  "type": "string"
+}
    • removedInput schema / properties / activationGroupId
      Removed value: -{
-  "description": "Activation group ID",
-  "format": "uuid",
-  "type": "string"
-}
    • addedInput schema / properties / activationMode
      Added value: +{
+  "description": "Conflict resolution mode",
+  "enum": [
+    "NONE",
+    "EXCLUSIVE",
+    "MAX_N"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / activationStrategy
      Added value: +{
+  "description": "Strategy when mode is EXCLUSIVE or MAX_N",
+  "enum": [
+    "FIRST_MATCH",
+    "HIGHEST_PRIORITY",
+    "MAX_BENEFIT"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / conflictResolutionMode
      Removed value: -{
-  "description": "Conflict resolution mode",
-  "enum": [
-    "NONE",
-    "EXCLUSIVE",
-    "MAX_N"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / conflictResolutionStrategy
      Removed value: -{
-  "description": "Strategy when mode is EXCLUSIVE or MAX_N",
-  "enum": [
-    "FIRST_MATCH",
-    "HIGHEST_PRIORITY",
-    "MAX_BENEFIT"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / executionLimit
      Added value: +{
+  "description": "Max rule executions (required when mode is MAX_N)",
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / maxSelections
      Removed value: -{
-  "description": "Max selections (required when mode is MAX_N)",
-  "minimum": 1,
-  "type": "integer"
-}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false), so the description carries the behavioral burden. It discloses that priority is auto-assigned, explains the cluster constraint (shared activationGroup must share activationMode/activationStrategy/executionLimit), and clarifies that executionLimit counts groups, not rules. This is rich behavioral context beyond what annotations provide.

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 compact, with no wasted words. It front-loads the core action ('Create a new policy group'), then states requirements, optional fields, and a key constraint in a logical order. Every sentence adds value and clarifies usage.

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 tool with 6 parameters and no output schema, the description is comprehensive. It covers the required field, auto-assignment behavior, optional conflict resolution and activation group settings, and explains the cluster constraints and executionLimit semantics. Combined with the fully detailed schema, an agent has everything needed to call it correctly.

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 100%, so descriptions already exist for each parameter. The description adds significant meaning about parameter relationships: priority auto-assignment, cluster consistency requirements, and the interpretation of executionLimit as groups rather than rules. This goes beyond the schema's per-field descriptions and helps an agent understand how parameters interact.

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 states 'Create a new policy group' with a clear verb and resource, and it distinguishes from sibling tools like update, delete, list, and reorder. It also highlights that priority is auto-assigned and points to lexq_groups_reorder for reordering, making the purpose unmistakable.

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

Usage Guidelines4/5

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

The description clearly indicates when to use this tool (to create a new group) and implicitly when not to (reordering is handled by lexq_groups_reorder). It provides context on cluster constraints and optional fields, giving an agent enough to decide when to set activationGroup and related options, though it does not explicitly list exclusion scenarios.

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

All LexQ toolsInspect
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