Skip to main content
Glama

skycloak_discover_oidc

Read-only

Resolve an OIDC issuer's discovery document to obtain authorization, token, and userinfo endpoints, then use the result when creating an identity provider.

Instructions

Resolve an OIDC issuer's discovery document to obtain its authorization, token, and userinfo endpoints. Use the result when creating an identity provider.

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": {
      "issuer_url": "<issuer_url>"
    },
    "name": "skycloak_discover_oidc"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuer_urlYesthe OIDC issuer URL

Output Schema

NameRequiredDescriptionDefault
issuerYes
jwks_uriNo
token_endpointYes
scopes_supportedNo
userinfo_endpointNo
authorization_endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe external read. The description adds the useful behavioral fact that the tool performs discovery resolution and surfaces specific endpoint types, but it omits failure modes (invalid/non-compliant discovery documents, timeouts) and does not state that nothing is persisted server-side. Given annotation coverage, a 3 is appropriate.

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 padding, and the core action is front-loaded before the usage hint. Every clause carries information an agent needs.

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?

The tool is a single-parameter lookup with an output schema, so return-value documentation is correctly delegated to the schema. The description is nearly complete; the only material gap is the absence of any guidance on invalid issuers or discovery failures, which matters for an open-world network call.

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?

Only one parameter, and the schema documents issuer_url at 100% coverage with a description matching the tool's own wording. The description adds no format details (scheme, trailing-slash handling, example value), so it neither compensates for nor harms the schema beyond the standard baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('Resolve') against a specific resource ('an OIDC issuer's discovery document') and names the concrete artifacts obtained (authorization, token, userinfo endpoints). It also positions itself relative to skycloak_create_identity_provider, so an agent can distinguish this lookup step from the create step without opening either schema.

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?

'Use the result when creating an identity provider' gives a clear downstream context but no real when/when-not guidance: nothing says whether this must be called before create_identity_provider, whether it can be reused for multiple providers, or what to do if the issuer is unreachable or non-conformant.

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