Skip to main content
Glama

skycloak_get_identity_provider

Read-only

Retrieve an identity provider's configuration by its provider ID within a specific Keycloak realm and cluster.

Instructions

Get an identity provider by provider 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>",
      "provider_id": "<provider_id>"
    },
    "name": "skycloak_get_identity_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
cluster_idYesthe cluster ID
provider_idYesthe identity provider alias, exactly as skycloak_list_identity_providers reports it (case-sensitive)

Output Schema

NameRequiredDescriptionDefault
TypeYes
EnabledYes
ProviderIDYes
DisplayNameYes

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=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no error/not-found behavior, no note that the provider must already exist, and no reconciliation of the unusual idempotentHint=false on what is otherwise a plain lookup.

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 short, front-loaded sentence with no filler or redundancy. It is efficient, though arguably too terse given the available room to clarify usage.

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 low-complexity with three fully documented required parameters and an output schema, so return values need not be described. Missing are the not-found/error semantics and any cue about when to reach for this rather than the list tool.

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 coverage is 100% and each parameter is documented, including the case-sensitivity and cross-reference to skycloak_list_identity_providers for provider_id. The description only restates the provider ID concept, so the baseline of 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?

The description states a specific verb and resource ('Get an identity provider') plus the lookup key ('by provider ID'), so an agent knows exactly what the tool returns. It does not distinguish itself from siblings such as skycloak_list_identity_providers or skycloak_get_realm, leaving that differentiation to the name alone.

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 statement of prerequisites, and no mention of alternatives like the list tool for discovery. The only implied usage cue is that the caller must already possess a provider ID.

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