Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

Cloudflare: list LB monitors

cf_lb_monitors_list
Read-only

List account Load Balancer health monitors (path, interval, retries, expected codes). Requires Account Load Balancers Read.

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo
zoneOrIdNoZone name (e.g. your-tenant.com) or zone ID to resolve account.id
accountIdNoCloudflare account ID; overrides CLOUDFLARE_ACCOUNT_ID and zone.account.id
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 / monitors
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "method": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  "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"
-}
    • 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: +[
+  "monitors",
+  "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.7/5.0
Behavior3/5

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

Annotations already establish that this is a safe read-only, non-destructive operation. The description adds the required Account Load Balancers Read permission, which is useful beyond annotations, but does not disclose pagination behavior, account/zone resolution behavior, or other operational traits.

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 two short sentences with no wasted text. The resource and scope are front-loaded, followed by the permission requirement.

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?

The description identifies the resource and the required permission, and an output schema exists to explain return values. It does not fully cover the multi-parameter account/zone routing context, but the schema carries most of that detail.

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?

The description mentions monitor attributes such as path, interval, retries, and expected codes, but these are not the input parameters. With schema coverage at 71% and no description of pagination or account/zone routing parameters beyond the schema, the description adds little parameter-level meaning.

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?

States a specific verb and resource: list account Load Balancer health monitors. The parenthetical examples (path, interval, retries, expected codes) clarify what monitor data is involved and distinguish this from load balancer or pool listing siblings.

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 gives a clear prerequisite (Account Load Balancers Read), which helps determine whether the caller can use it. However, it does not explicitly say when to choose this over siblings like cf_load_balancers_list or cf_lb_pools_list, leaving usage mostly implied by the resource name.

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