Skip to main content
Glama

skycloak_get_siem_destination

Read-only

Retrieve a SIEM destination by ID to inspect its configuration and details.

Instructions

Get a SIEM destination by ID.

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": {
      "destination_id": "<destination_id>"
    },
    "name": "skycloak_get_siem_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
destination_idYesthe SIEM destination ID

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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, and the description adds nothing beyond that profile – no mention of behavior for unknown IDs, no note that the response includes destination configuration, no scoping caveats. It essentially restates the title.

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?

A single front-loaded sentence with zero filler, appropriate for a simple getter. It is efficient but borders on under-specified, so it is not a maximal conciseness score.

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?

Tool complexity is low, annotations cover the safety profile, and an output schema exists so return values need not be described. However, nothing tells the agent what happens on an invalid or missing ID, which is the main behavioral gap for a lookup tool.

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 parameter with 100% schema description coverage ('the SIEM destination ID'), so the schema already carries the semantics. The description only echoes the ID requirement and adds no format, source, or validity information beyond it.

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 states a specific verb and resource ('Get a SIEM destination') and adds the 'by ID' qualifier, which cleanly separates it from the sibling list tool and the create/update/delete/test siblings. It stops short of naming any sibling explicitly, which keeps it at 4 rather than 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 ID' signals a single-record lookup that requires a known identifier, so an agent can infer it should use skycloak_list_siem_destinations to find IDs first. There is no explicit when-to-use, prerequisite, or exclusion statement.

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