Skip to main content
Glama

skycloak_test_identity_provider

Tests connectivity to a Keycloak identity provider in a realm, with optional one-time client ID and secret overrides to verify credentials without changing stored configuration.

Instructions

Test connectivity to an identity provider, optionally overriding the client credentials for this test only.

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_test_identity_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
client_idNooverride client ID for this test only
cluster_idYesthe cluster ID
provider_idYesthe identity provider alias, exactly as skycloak_list_identity_providers reports it (case-sensitive)
client_secretNooverride client secret for this test only

Output Schema

NameRequiredDescriptionDefault
messageNo
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, and the description usefully reinforces this by framing the call as a connectivity test and stating that credential overrides are scoped to "this test only" (no persistence). It does not disclose failure behavior, timeouts, or rate limits, which would be the remaining useful detail.

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 the action first and the optional override clause second; nothing is redundant. It is arguably too terse for a network-touching test operation, but no sentence 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?

With an output schema present, return values need no explanation, and the three required identifiers are fully documented in the schema. The description covers the essential scope (test + non-persistent overrides); only failure/timeout semantics are missing, which is a minor gap.

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% and each parameter already carries a description, so the baseline is 3. The description's only added semantic is that the client_id/client_secret overrides are ephemeral, which the schema itself already states, so it contributes little beyond the structured fields.

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 names a specific verb+resource combination ("test connectivity to an identity provider"), which is clearly distinct from the create/get/update/delete identity-provider siblings. It does not explicitly contrast itself with a sibling such as skycloak_get_identity_provider, but the action is unambiguous.

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: run this to verify an IdP works, optionally with alternate credentials. There is no explicit statement of when to prefer this over skycloak_get_identity_provider or when not to use it (e.g. before the provider is fully configured), and no prerequisites such as required permissions are given.

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