Skip to main content
Glama

skycloak_get_cluster_security

Read-only

Retrieves a cluster's edge-security configuration, including IP allow-listing, rate limiting, WAF, geo-blocking, and bot management, to review and verify protections.

Instructions

Get a cluster's edge-security configuration: 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_get_cluster_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesthe cluster ID

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, so the safety profile is supplied structurally. The description adds the useful content that the response covers five distinct security domains, but says nothing about permissions needed, error behavior, or whether settings are returned as effective or configured values. With annotations carrying the safety burden, this is adequate but not rich.

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?

A single front-loaded sentence with the resource and its enumerated scope, and no filler. Every clause earns its place by telling the agent what configuration domains come back.

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?

This is a simple one-parameter read with annotations and an output schema, so return values need no explanation here. The description covers the resource and the scope of what is returned, which is sufficient to call it correctly. Only minor operational detail (permissions, empty-state behavior) is missing.

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?

There is a single required parameter (cluster_id) with 100% schema description coverage, so the schema already does the work and the baseline of 3 applies. The description adds no meaning about the identifier's format, source, or lookup implications. No further semantic value is contributed beyond the schema.

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?

The description names a specific verb ('Get') and resource ('a cluster's edge-security configuration') and then enumerates the concrete sub-areas covered: IP allow-listing, rate limiting, WAF, geo-blocking, and bot management. That enumeration distinguishes it from the broad skycloak_get_cluster and from skycloak_get_security_logs without naming them. It stops short of an explicit sibling contrast (e.g., 'use skycloak_update_cluster_security to modify'), which keeps it from a 5.

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?

Usage is only implied by the read verb and the subject matter; there is no statement of when to reach for this versus skycloak_get_cluster or skycloak_get_security_logs. There are also no preconditions or exclusions (e.g., required role, behavior when no security config exists). An agent can infer the read-only inspection use case, but the description does not guide selection.

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