Skip to main content
Glama

skycloak_create_siem_destination

Create a SIEM destination to forward Keycloak events, application logs, security logs, or audit data to syslog, S3, or HTTP endpoints; credentials are write-only and never returned.

Instructions

Create a SIEM destination. Credentials are write-only and are not returned.

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": {
      "name": "<name>",
      "type": "<type>",
      "source": "<source>"
    },
    "name": "skycloak_create_siem_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
s3No
httpNo
nameYes
typeYesdestination transport: syslog, s3, or http (case-insensitive)
batchNo
sourceYes
syslogNo

Output Schema

NameRequiredDescriptionDefault
idYes
s3No
httpNo
nameYes
typeYes
batchYes
sourceYes
syslogNo
enabledYes
created_atYes
last_errorNo
updated_atYes
last_sent_atNo
failure_countYes
health_statusYes
total_logs_sentYes
total_bytes_sentYes
total_events_sentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world mutation. The description adds genuinely useful context beyond that: credentials are write-only and never returned, which tells the agent not to expect secrets back on subsequent reads. However, it omits other important behavior for a create tool, such as what happens on duplicate names and why it is not idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the one non-obvious behavioral fact. There is no wasted wording, though the brevity here reflects under-specification rather than tight editing.

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

Completeness2/5

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

This is a complex tool with 7 parameters, required nested objects, and a type-dependent shape (s3/http/syslog blocks that must match the type field), none of which the description hints at. An output schema exists so return values need not be described, but the input-side complexity is left almost entirely unexplained.

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?

Schema description coverage is only 14%, so the description carries most of the burden for explaining 7 parameters, including nested type-dependent objects, and it explains none of them. The only parameter-adjacent statement is that credentials (access_key_id, secret_access_key, password, bearer_token) are write-only, which is useful but does not compensate for the large coverage gap.

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 and resource ("Create a SIEM destination"), which is unambiguous and separable from sibling operations like get/update/delete/test/list_siem_destination by verb alone. It does not explicitly name or contrast those siblings, so it falls short of 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 Guidelines2/5

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

There is no guidance on when to create versus update an existing destination, no mention of validating a destination first with skycloak_test_siem_destination, and no stated prerequisites or permissions. The agent must infer all routing and sequencing decisions on its own.

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