Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

Cloudflare: Transform Rules replace

cf_transform_rules_replace
Destructive

Replace Transform Rules for a phase with the provided full rules array.

Input Schema

NameRequiredDescriptionDefault
zoneYesZone name (e.g. your-tenant.com) or zone ID
phaseNohttp_request_transform
rulesYesComplete Cloudflare transform rules array
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
descriptionNo
account_slugNoCloudflare account slug. Required when the workspace has multiple accounts and the zone is not yet cataloged.
environment_slugNoCloud Catalog environment used as an account-routing preference when no zone is provided.

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed25 schema fields changed
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -trueNew value: +false
    • removedOutput schema / properties / data / properties / count
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / data / properties / description
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / data / properties / errors / items / $ref
      Removed value: -"#/properties/data/properties/result/anyOf/0/items"
    • addedOutput schema / properties / data / properties / errors / items / additionalProperties
      Added value: +false
    • addedOutput schema / properties / data / properties / errors / items / properties
      Added value: +{
+  "code": {
+    "type": "integer"
+  },
+  "message": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / data / properties / errors / items / required
      Added value: +[
+  "message"
+]
    • addedOutput schema / properties / data / properties / errors / items / type
      Added value: +"object"
    • addedOutput schema / properties / data / properties / gaps
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / properties / id
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / data / properties / items
      Removed value: -{
-  "$ref": "#/properties/data/properties/result/anyOf/0"
-}
    • addedOutput schema / properties / data / properties / lastUpdated
      Added value: +{
+  "format": "date-time",
+  "type": "string"
+}
    • removedOutput schema / properties / data / properties / messages
      Removed value: -{
-  "items": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "$ref": "#/properties/data/properties/result/anyOf/0/items"
-      }
-    ]
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / data / properties / name
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / data / properties / partial
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / data / properties / phase
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / data / properties / result
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": true,
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "$ref": "#/properties/data/properties/result/anyOf/0/items"
-    }
-  ]
-}
    • removedOutput schema / properties / data / properties / result_info
      Removed value: -{
-  "$ref": "#/properties/data/properties/result/anyOf/0/items"
-}
    • addedOutput schema / properties / data / properties / rules
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "type": "string"
+      },
+      "childRulesetId": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "enabled": {
+        "type": "boolean"
+      },
+      "expression": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "ref": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "enabled"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / properties / truncated
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / data / properties / version
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / data / properties / warnings
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / required
      Added value: +[
+  "rules",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]
    • addedOutput schema / properties / dataSchemaVersion
      Added value: +{
+  "const": 2,
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true. The description adds value by signaling that replacing is done with the FULL rules array, implying existing rules are overwritten. However it does not state auth requirements, irreversibility, or live-traffic impact, so the added context is modest for a destructive mutation.

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?

A single efficient sentence with the replacement semantics front-loaded and no wasted words. It is lean, though arguably under-specified rather than concise.

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?

This is a destructive, 7-parameter mutation with an output schema (so returns need no explanation), yet the description omits prerequisites like account resolution, phase behavior, and what replacement means for existing rules. For a destructive operation the context provided is thin.

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?

Schema coverage is 71%, so most parameters are documented in the schema. The description references 'phase' and 'full rules array' (matching the phase and rules params) but says nothing about zone, account_slug, context_id, or environment_slug, leaving the routing/routing-preference params undocumented anywhere. Baseline 3 fits.

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?

States a specific verb (Replace), resource (Transform Rules), and scope (per phase, full array), which distinguishes it from cf_transform_rules_list. It does not explicitly differentiate from sibling *_replace tools like cf_redirect_rules_replace or cf_config_rules_replace, but the resource is clear enough.

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 on when to use this versus cf_transform_rules_list or the other *_replace endpoints, and no prerequisites (permissions, phase semantics, warning that it overwrites existing rules) are noted. The agent must infer usage from the name alone.

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

All Opsphere — DevOps & SRE Intelligence 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