Skip to main content
Glama

skycloak_test_siem_destination

Sends a test event to a specified SIEM destination to verify its connection and confirm that events are delivered correctly.

Instructions

Send a test event to a SIEM destination.

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

Input Schema

NameRequiredDescriptionDefault
destination_idYesthe SIEM destination ID

Output Schema

NameRequiredDescriptionDefault
messageNo
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-destructive but externally visible write that is not idempotent. The description only restates the "test event" idea and adds nothing about what payload is sent, whether repeated calls produce duplicate events downstream, or how delivery failures surface.

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 zero filler. Nothing is redundant; the only issue is under-specification, which is measured in the other dimensions rather than here.

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?

The tool is structurally simple (one required param, output schema present, no nested objects), so the return value does not need explaining. However, for an externally visible, non-idempotent test action, the definition says nothing about what the destination receives or what a failed test means, leaving the agent to infer it.

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 with full schema description coverage, so the schema already defines destination_id. The description adds no format, source-of-truth, or lookup hint beyond that, which is the expected baseline when schema coverage is 100%.

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 ("Send a test event to a SIEM destination"), which is enough to distinguish it from create/delete/get/update SIEM destination siblings and from test tools for other resources like smtp or webhook subscriptions. It stops short of an explicit contrast, but the purpose is unambiguous.

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?

It gives no guidance on when to use this tool versus the other skycloak_test_* siblings, no prerequisites (must the destination exist and be enabled?), and no mention of side effects such as an alert appearing downstream. The only usage signal is the word "test" in the name.

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