Skip to main content
Glama

skycloak_get_security_logs

Read-only

Read recent WAF security logs for a cluster to inspect blocked requests, attack types, and source IPs, with free-text search and a limit on returned entries.

Instructions

Read recent security (WAF) logs for a cluster — blocked requests, attack types, source IPs.

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_security_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax entries to return (default 50)
searchNofree-text search
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
logsYes
countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, closed-world, and non-idempotent behavior. The description adds useful scope by naming WAF log contents, but it does not disclose retention limits, pagination behavior, auth requirements, or how "recent" is defined.

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 description is a single front-loaded sentence with an efficient dash-list of log contents. Every element earns its place and nothing is repeated from the annotations or schema.

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 full schema, annotations, and an output schema, the definition is mostly complete. The description supplies the log scope and payload summary, though it leaves out the distinction from generic logs and the meaning of "recent."

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 cluster_id, limit, and search are already documented in the input schema. The description adds no parameter-specific semantics beyond what the schema provides, matching 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?

The description gives a specific verb and resource: "Read recent security (WAF) logs for a cluster," and enumerates blocked requests, attack types, and source IPs. This distinguishes it from generic log access, though it does not explicitly name the sibling tool it differs from.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no mention of alternatives such as skycloak_get_logs or skycloak_get_cluster_security. The context is implied by "security (WAF) logs" but the agent must infer when this tool is preferred.

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