Skip to main content
Glama

skycloak_get_logs

Read-only

Read recent Keycloak server logs for a cluster, filtered by log level or free-text search, to troubleshoot issues and inspect runtime activity.

Instructions

Read recent Keycloak server logs for a cluster, optionally filtered by level and a search string.

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

Input Schema

NameRequiredDescriptionDefault
levelNofilter by log level: info, warn, error, or debug (case-insensitive)
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

A3.5/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 covered. The description adds the word 'recent', which hints at a bounded time window rather than a full log archive, but it does not say how far back 'recent' reaches or whether results are truncated. With annotations carrying the safety burden, a 3 is appropriate.

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 sentence with zero waste: verb, resource, scope, then the optional filters. The scoping constraint (which cluster) is front-loaded ahead of the optional refinements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover read safety. What is still missing is the meaning of 'recent' (the effective time window) and any indication of truncation or result caps, which matter for a log-reading tool that agents will rely on for diagnosis.

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 coverage is 100%, so level, limit, search and cluster_id are all documented in the schema itself. The description restates that level and search act as filters and that cluster_id scopes the read, but adds no syntax, format or default information beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb ('Read') with a specific resource ('Keycloak server logs') and states the scoping unit ('for a cluster'). It implicitly separates itself from the sibling skycloak_get_security_logs by naming 'server logs', but it never explicitly contrasts the two, so an agent must infer the boundary.

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 phrase 'optionally filtered by level and a search string' implies the intended use case of narrowing down recent log output, which is useful context. However, there is no explicit when-to-use versus when-not guidance and no mention of the obvious alternative, skycloak_get_security_logs, so the agent is left to infer routing.

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