Opsphere — DevOps & SRE Intelligence

Cloudflare: Snippet rules

cf_snippet_rules_list

Read-only

List Snippet rules for a zone (GET /snippets/snippet_rules). Optional snippetId filters by snippet name.

Input Schema

Name	Required	Description
`zone`	Yes	Zone name (e.g. your-tenant.com) or zone ID
`snippetId`	No	Optional snippet name filter from cf_snippets_list
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`account_slug`	No	Cloudflare account slug. Required when the workspace has multiple accounts and the zone is not yet cataloged.
`environment_slug`	No	Cloud Catalog environment used as an account-routing preference when no zone is provided.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedOct 26, 2026

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"
+]

First observedOct 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the endpoint and the optional filter behavior; it does not discuss pagination, zone requirements, or other behavioral traits beyond that.

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 definition is a single tight sentence plus one optional-filter clause. The core purpose and endpoint are front-loaded, and there is no wasted text.

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?

With a complete input schema, an output schema, and annotations covering safety, the description provides enough to call the tool correctly. It could be stronger if it clarified how this differs from cf_snippets_list, but the essential behavior is present.

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 description coverage is 100%, so the schema already documents all five parameters. The description repeats that snippetId filters by snippet name, which matches the schema's own wording rather than adding new meaning, so the baseline 3 is appropriate.

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 clear verb and resource ("List Snippet rules for a zone") and includes the underlying endpoint. It is understandable in isolation, but it does not explicitly distinguish itself from the closely named sibling cf_snippets_list.

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

Usage Guidelines3/5

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

The description implies the tool's use for listing snippet rules and notes the optional snippetId filter. However, it gives no explicit when-to-use guidance, no exclusions, and no comparison to cf_snippets_list or other rule-listing siblings.

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 tools Inspect

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

Need Help?