Skip to main content
Glama

skycloak_update_domain_route

Idempotent

Update a domain route's admin access setting and allowed CORS origins for a Skycloak cluster.

Instructions

Update a domain route's admin access and CORS origins.

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>",
      "domain_id": "<domain_id>",
      "route_id": "<route_id>"
    },
    "name": "skycloak_update_domain_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
route_idYesthe route ID
domain_idYesthe domain ID
cluster_idYesthe cluster ID
allow_admin_accessNowhether the admin console is reachable
cors_allowed_originsNoCORS origins allowed via this domain

Output Schema

NameRequiredDescriptionDefault
idYes
realmYes
hide_realm_pathYes
allow_admin_accessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds the scope of mutable fields but does not explain partial-update behavior, permission requirements, or side effects. It does not contradict the annotations.

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?

A single front-loaded sentence with no unnecessary wording. It is appropriately sized for the tool's purpose.

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?

An output schema exists, annotations are rich, and the input schema is fully documented, so the description need not explain return values. It covers the purpose and mutable fields adequately, though it omits explicit partial-update semantics and usage context.

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%, so the input schema already documents all five parameters. The description names admin access and CORS origins but adds no format or semantic detail beyond what the schema provides, making the baseline 3 appropriate.

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 ('Update') and resource ('domain route'), and names the two mutable fields: admin access and CORS origins. It does not explicitly differentiate itself from sibling update tools or from create/delete/get domain route tools, so it falls short of a 5.

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?

Provides no when-to-use guidance, no prerequisites, and no alternatives. It only implies that this tool updates an existing domain route, leaving the agent to infer the appropriate context.

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