Skip to main content
Glama

skycloak_list_identity_providers

Read-only

List SSO identity providers across a realm, cluster, or entire fleet; omit realm and cluster_id to answer fleet-wide SSO questions in one call.

Instructions

List the identity providers (SSO connections) in a realm. Omit realm to cover every realm, and cluster_id to cover every cluster, so one call can answer an SSO question across the whole fleet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skycloak_list_identity_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmNothe realm name whose identity providers to list. Omit to search every realm
cluster_idNothe ID of the cluster. Omit to search every cluster in the workspace

Output Schema

NameRequiredDescriptionDefault
countYes
unreachableNo
identity_providersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: omitting the optional filters widens the query to every realm and every cluster in a single call, which tells the agent this can be a broad, high-volume read. It does not mention pagination, result caps, or ordering, which is the main remaining gap.

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?

Two sentences, zero filler, with the core purpose front-loaded and the scope/escalation guidance immediately after. Every clause earns its place and nothing is repeated verbatim from the title.

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?

With only two optional parameters, an output schema present, and full annotation coverage, this description supplies what an agent needs to choose a scoped versus fleet-wide call. The only missing element is any hint about result size or paging when the call spans every realm and cluster.

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 both schema properties already state 'Omit to search every realm' / 'Omit to search every cluster'. The description's parameter discussion largely restates those semantics, adding emphasis rather than new meaning such as name formatting or matching behavior. Baseline 3 applies when the schema carries the parameter burden.

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 gives a specific verb and resource ('List the identity providers') and even glosses the jargon as '(SSO connections) in a realm', so the agent knows exactly what is returned. It does not explicitly contrast itself with skycloak_get_identity_provider or skycloak_list_identity_provider_templates, so sibling differentiation is left implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly explains the two usage modes: supply realm/cluster_id for a scoped listing, or omit both to fan out across the whole fleet ('one call can answer an SSO question across the whole fleet'). That is concrete when-to-use guidance for both variants, though there are no explicit when-not conditions or named alternatives.

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