Skip to main content
Glama

skycloak_update_extension

Idempotent

Update a custom extension's name or description by passing its extension ID and new values, keeping extension metadata accurate in Skycloak.

Instructions

Update a custom extension's name or description.

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": {
      "extension_id": "<extension_id>"
    },
    "name": "skycloak_update_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNonew name
descriptionNonew description
extension_idYesthe extension ID

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
sourceYes
versionNo
descriptionNo
documentation_urlNo
keycloak_versionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the mutation is non-destructive, idempotent, and non-open-world, so the safety profile is covered. The description adds the useful constraint that only metadata (name/description) is touched, implying code is untouched, but says nothing about permissions, partial-update behavior for omitted fields, or failure cases.

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 no filler or redundancy. It is efficient, though its brevity borders on under-specification given the tool's role in a large sibling family.

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?

With annotations covering safety and an output schema covering returns, the remaining need is guidance on partial updates and relationship to upgrade/install. The description omits both, leaving it minimally adequate for a 3-parameter mutation tool in a crowded namespace.

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 description coverage is 100% and the schema already labels name, description, and extension_id, so the description merely restates the field list. It adds no extra semantics such as whether omitted fields are left unchanged, whether empty strings clear values, or name uniqueness constraints.

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 custom extension') plus the exact mutable fields (name or description), which distinguishes it from code-level siblings like skycloak_upgrade_extension. It does not explicitly name those alternatives, so sibling differentiation is only implied by the field list.

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?

The description gives no when-to-use or when-not-to-use guidance, no mention of switching to upgrade/install/uninstall operations, and no prerequisites such as the extension needing to exist or be installed. An agent must infer all routing from the tool name alone.

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