Skip to main content
Glama

skycloak_get_application

Read-only

Retrieve an OIDC or SAML application by client ID from a Keycloak realm to inspect its configuration and details.

Instructions

Get an application (OIDC/SAML client) by client 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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "client_id": "<client_id>"
    },
    "name": "skycloak_get_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
client_idYesthe application client ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
NameYes
TypeYes
StatusYes
ClientIDYes
ProtocolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds only the OIDC/SAML domain gloss; it says nothing about behavior on a missing client ID, whether secrets/credentials appear in the response, or scoping across cluster/realm — context that would matter for an admin-style get.

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 sentence with verb and resource front-loaded and zero filler; every word carries information and nothing is repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter get with full schema coverage, complete annotations, and an output schema that documents return values, the description is nearly sufficient. The remaining gap is behavioral (what happens when the client ID does not exist), which is minor at this complexity.

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 realm, client_id, and cluster_id are fully documented in the schema. The description reinforces that the lookup key is the client ID but adds no semantics beyond that, which is the expected baseline when the schema does the work.

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 ("Get an application") and adds a useful gloss — "(OIDC/SAML client)" — plus the lookup key "by client ID". An agent can tell this is a single-resource retrieval keyed by client ID, though it does not explicitly distinguish itself from siblings like skycloak_list_application_roles or skycloak_get_application_role.

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 implied rather than stated: "by client ID" signals that a known client_id is a prerequisite and that this is the point-lookup counterpart to listing tools. There is no explicit when-to-use/when-not guidance and no alternative named (e.g., use list_* when the client ID is unknown).

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