Skip to main content
Glama

skycloak_list_extensions

Read-only

Lists the extension catalog available to a workspace, showing marketplace extensions that can be installed on a cluster.

Instructions

List the extension catalog available to the workspace (marketplace extensions that can be installed on a cluster).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
extensionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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. The description contributes the workspace-level, catalog-not-cluster scoping, but says nothing about result volume, ordering, or pagination behavior beyond what the output schema carries.

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 resource stated first and the clarifying parenthetical after it. The parenthetical partly restates "catalog," but it earns its place by defining what counts as an extension.

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?

For a parameterless read-only list tool with annotations and an output schema present, the description covers what the tool returns conceptually and its scope. The only shortfall is the missing explicit contrast with the cluster-extension listing sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning for the description to supply. The description correctly adds no parameter prose, keeping the definition aligned with the empty schema.

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 and resource ("List the extension catalog") and the parenthetical clarifies scope: marketplace extensions installable on a cluster, available to the workspace. That phrasing implicitly distinguishes it from the cluster-scoped sibling, but it never names that sibling or states the contrast explicitly.

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?

The description implies usage — browse the installable catalog — but gives no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g., that this is the discovery step before installing on a cluster). With a near-identical sibling (skycloak_list_cluster_extensions) in the catalog, an explicit routing sentence would have helped.

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