Skip to main content
Glama

skycloak_update_application

Idempotent

Update an application's display name, description, or redirect URIs in a Skycloak Keycloak realm by specifying its cluster, realm, and client ID.

Instructions

Update an application's name, description, or redirect URIs.

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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "client_id": "<client_id>"
    },
    "name": "skycloak_update_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNonew display name
realmYesthe Keycloak realm name
client_idYesthe application client ID
cluster_idYesthe cluster ID
descriptionNonew description
redirect_urisNoreplace the full set of redirect URIs

Output Schema

NameRequiredDescriptionDefault
NameYes
TypeYes
StatusYes
ClientIDYes
ProtocolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 nothing beyond that: it does not say whether the update is partial (only supplied fields change) or a full replace, whether name changes break existing sessions, or what permissions are required.

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?

One short, front-loaded sentence with no wasted wording. Its brevity is appropriate, though it is close to under-specification for a mutation tool rather than tight conciseness.

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 a simple, idempotent mutation with an output schema and full parameter documentation, so most of the burden is carried by structured fields. However, the description should still clarify partial-vs-full update semantics and precedence when required identifiers conflict with mutable fields, which it does not.

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%, so each of the six parameters is already documented, including the note that redirect_uris replaces the full set. The description merely re-lists three of those fields and adds no format, validation, or omission semantics beyond the schema, so baseline 3 applies.

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 (Update) plus the resource (an application) and enumerates the mutable fields (name, description, redirect URIs). This distinguishes it from siblings like skycloak_update_application_role or skycloak_rotate_application_secret, though it never explicitly contrasts itself with them.

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 when-to-use guidance, no prerequisites (cluster/realm/client must exist), and no mention of alternatives such as skycloak_create_application for new clients or skycloak_get_application to read current values. Usage is only implied by the verb 'Update'.

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