Skip to main content
Glama

skycloak_update_cluster_security

Idempotent

Update a cluster's edge-security settings selectively: configure IP allow-listing, rate limiting, WAF, geo-blocking, or bot management without overwriting CAPTCHA or other unprovided sections.

Instructions

Update a cluster's edge-security configuration. Only the sections you provide are changed; CAPTCHA settings are preserved. Supports IP allow-listing, rate limiting, WAF, geo-blocking, and bot management.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_id": "<cluster_id>"
    },
    "name": "skycloak_update_cluster_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
wafNoweb application firewall settings
cluster_idYesthe cluster ID
geo_blockingNocountry-based access control
rate_limitingNorequest-rate ceilings
bot_managementNobot detection and challenge settings
ip_access_controlNoper-path IP allow rules

Output Schema

NameRequiredDescriptionDefault
wafNo
geo_blockingNo
rate_limitingNo
bot_managementNo
ip_access_controlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare mutation, idempotency, and non-destructiveness; the description adds the crucial detail that omitted sections are left untouched rather than reset, which is exactly what an agent needs to reason about partial updates. It does not cover permission requirements or response shape, but an output schema exists to carry the latter.

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?

Three short sentences, front-loaded with the action and immediately followed by the most operationally important constraint (partial update semantics). No filler or redundant restatement of the name.

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?

For a 6-parameter mutation tool with full schema coverage, annotations, and an output schema, the description supplies the one thing structured fields do not: that the update is section-scoped and non-destructive to unspecified configuration. Only the absence of any auth/permission or CAPTCHA-alternative pointer leaves a minor gap.

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% with nested field-level descriptions, so the schema carries the parameter burden. The description's feature list (IP allow-listing, rate limiting, WAF, geo-blocking, bot management) maps loosely onto the five top-level section parameters and adds modest interpretive value, but no new constraints.

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 (Update) and resource (a cluster's edge-security configuration) and enumerates the covered capability areas. That scope separates it from the broader skycloak_update_cluster and the read-only skycloak_get_cluster_security, though no sibling is named explicitly.

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?

'Only the sections you provide are changed' gives clear patch-style usage context, and 'CAPTCHA settings are preserved' implies a boundary the agent should not cross with this tool. It stops short of naming an alternative for CAPTCHA edits or recommending a read via skycloak_get_cluster_security before updating.

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

Deploy Server

Other Tools