Skip to main content
Glama
AutomoxCommunity

Automox MCP Server

by AutomoxCommunity
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Apply Policy Changes

apply_policy_changes
Destructive

Create or update Automox policies with automatic format correction to ensure valid configurations.

Instructions

Create or update Automox policies with automatic format correction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
previewNo
operationsYes
request_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metadataNoPagination, errors, per-section summaries, token-budget warnings, and correlation metadata. Shape varies per call.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv2.2.0
    • addedOutput schema / description
      Added value: +"Structured output of the ``apply_policy_changes`` tool."
    • addedOutput schema / properties
      Added value: +{
+  "data": {
+    "anyOf": [
+      {
+        "additionalProperties": true,
+        "properties": {
+          "operations": {
+            "anyOf": [
+              {
+                "items": {
+                  "additionalProperties": true,
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null,
+            "description": "Per-operation result; each carries action, policy fields, and request body",
+            "title": "Operations"
+          },
+          "preview": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null,
+            "description": "True when no write was performed (dry-run review)",
+            "title": "Preview"
+          }
+        },
+        "title": "PolicyChangeData",
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "metadata": {
+    "anyOf": [
+      {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Pagination, errors, per-section summaries, token-budget warnings, and correlation metadata. Shape varies per call.",
+    "title": "Metadata"
+  }
+}
    • addedOutput schema / title
      Added value: +"PolicyChangeResult"
  2. First observedv2.0.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already indicate destructive behavior (destructiveHint: true). The description adds that it performs automatic format correction, but does not detail what that entails, what gets destroyed, or any authentication requirements. It adds some context but not extensive.

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?

The description is a single sentence, concise but under-specified. It conveys the core action but could include more detail without being verbose. The structure is fine but does not earn extra points for completeness.

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

Completeness2/5

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

Given the presence of an output schema, the description still lacks important context like error handling, idempotency, scope of operation, and what 'automatic format correction' implies. It is not complete for a mutation tool with potential destructive effects.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the parameters (operations, preview, request_id). The agent must rely on parameter names alone, which are somewhat self-explanatory but lack specifics about the structure of operations objects or the effect of preview.

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

Purpose4/5

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

The description clearly states it creates or updates Automox policies, with automatic format correction. It distinguishes from read tools and other policy manipulation tools like clone_policy, delete_policy. However, it doesn't specify if it applies to all policies or a subset.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when to use preview mode, or when to prefer other policy tools like create_policy or update_policy.

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/AutomoxCommunity/automox-mcp'

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