Skip to main content
Glama

skycloak_list_applications

Read-only

Lists the OIDC and SAML client applications in a specified realm, helping you inspect configured identity integrations for a cluster.

Instructions

List the OIDC/SAML clients (applications) in a realm.

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>"
    },
    "name": "skycloak_list_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe realm name whose applications to list
cluster_idYesthe ID of the cluster

Output Schema

NameRequiredDescriptionDefault
countYes
applicationsYes

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description adds useful scoping context (results are confined to a single realm, and "applications" means OIDC/SAML clients), but says nothing about pagination, result ordering, or the oddly-flagged idempotentHint=false.

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 zero filler, and the key clarification that applications are OIDC/SAML clients is placed where it is read first. It is perhaps too terse for the job it must do, but nothing in it is wasted.

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?

This is a simple two-parameter read tool with full schema coverage, an output schema, and informative annotations, so the description does not need to explain return values. What remains thin is guidance on choosing it over sibling list tools, but for a tool of this complexity the definition is largely sufficient.

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%, with both realm and cluster_id documented in the schema itself. The description adds no meaning beyond that baseline — it does not explain the relationship between cluster and realm or any format expectations, so it neither compensates nor detracts.

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 (List) and resource (OIDC/SAML clients, explicitly glossed as "applications") scoped to a realm, which is clear enough for an agent to act on. It does not, however, distinguish itself from siblings such as skycloak_list_application_roles or skycloak_list_application_sessions, which also operate on application data.

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 explicit when-to-use guidance, no exclusions, and no pointer to an alternative tool. The only usage signal is the implicit requirement of a realm context, which an agent must infer from the phrase "in a realm."

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