Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

Cloudflare: zone settings

cf_zone_settings_get
Read-only

Get zone settings. Omit settingId for all settings; pass settingId (e.g. ssl, security_level, hsts) for one.

Input Schema

NameRequiredDescriptionDefault
zoneYesZone name (e.g. your-tenant.com) or zone ID
settingIdNoSetting id (e.g. ssl, security_level, always_use_https)
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
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. Changed16 schema fields changed
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -trueNew value: +false
    • removedOutput schema / properties / data / properties / count
      Removed value: -{
-  "type": "number"
-}
    • removedOutput schema / properties / data / properties / errors
      Removed value: -{
-  "items": {
-    "$ref": "#/properties/data/properties/result/anyOf/0/items"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / data / properties / gaps
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / data / properties / items
      Removed value: -{
-  "$ref": "#/properties/data/properties/result/anyOf/0"
-}
    • 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 / partial
      Added value: +{
+  "type": "boolean"
+}
    • 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 / settings
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "value": {
+        "type": [
+          "string",
+          "number",
+          "boolean"
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / data / properties / success
      Removed value: -{
-  "type": "boolean"
-}
    • addedOutput schema / properties / data / properties / truncated
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / data / properties / warnings
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / required
      Added value: +[
+  "settings",
+  "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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the all-vs-single retrieval semantics and says nothing about response shape, errors, or permission needs; with annotations carrying the load, this is an adequate 3.

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?

Two short clauses, the primary action first and the conditional parameter rule second. Nothing is redundant and nothing is buried.

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?

An output schema exists and all parameters are described in the schema, so the description does not need to cover returns or routing fields. The one thing it could have added — how this differs from cf_ssl_mode_get or cf_zone_status — is missing, but for a simple read tool what is present is close to sufficient.

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 all five parameters including zone, context_id, account_slug and environment_slug are documented in the schema. The description's settingId examples (ssl, security_level, hsts) largely restate what the schema already shows, so it adds little beyond the baseline.

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 and resource ('Get zone settings') and immediately clarifies the two retrieval modes. It does not name or distinguish itself from nearby siblings such as cf_ssl_mode_get or cf_zone_status, so an agent must infer the boundary from the name alone.

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?

Explicitly says 'omit settingId for all settings; pass settingId ... for one', which resolves the only branching decision in the call. It offers no when-to-use-this-vs-a-sibling guidance, so it stops short of a 5.

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