Skip to main content
Glama

skycloak_update_siem_destination

Idempotent

Update an existing SIEM destination by changing only the fields you provide, such as source, batching, or transport settings; credentials stay write-only.

Instructions

Update a SIEM destination. Only provided fields are changed; credentials remain write-only.

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

Input Schema

NameRequiredDescriptionDefault
s3No
httpNo
nameNo
batchNo
sourceNo
syslogNo
enabledNo
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
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond those: partial-update semantics ('only provided fields are changed') and that credential fields are write-only and not returned. It stops short of saying what happens on an invalid destination_id or whether re-submitting is safe in concurrent edits.

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?

Two short sentences with the action front-loaded and the two behavioral caveats immediately after. No filler, no restatement of the title, and nothing extraneous to trim.

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?

For a mutation tool with 8 parameters, deeply nested configuration blocks, and near-zero schema description coverage, two sentences leave major gaps. Nothing tells the agent how the mutually distinct s3/http/syslog destination blocks should be chosen or whether they replace existing configuration, which is exactly the ambiguity this description needed to resolve. Output schema exists, so return values need not be explained.

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 13% across 8 parameters, several of them nested objects (s3, http, syslog, source, batch), so the description carries most of the burden and does not meet it. It says nothing about which transport block to supply, how the s3/http/syslog variants relate, or how source filtering fields behave. The only parameter-relevant statement is that credentials are write-only.

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: 'Update a SIEM destination.' An agent can tell this apart from skycloak_create_siem_destination and skycloak_delete_siem_destination by the verb alone. It does not, however, distinguish itself from skycloak_test_siem_destination or skycloak_get_siem_destination beyond the obvious verb difference.

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 call this versus the create/delete/test siblings, no prerequisites, and no exclusions. The sentence 'Only provided fields are changed' describes behavior rather than when-to-use, so the agent must infer routing from the tool 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