Skip to main content
Glama

skycloak_get_domain_route

Read-only

Retrieve a single realm route on a custom domain using cluster, domain, and route IDs.

Instructions

Get a single realm route on a custom domain.

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

Input Schema

NameRequiredDescriptionDefault
route_idYesthe route ID
domain_idYesthe domain ID
cluster_idYesthe cluster ID

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

C2.7/5.0
Behavior2/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens when a route ID does not exist, whether the route is scoped to a cluster, or what a returned route contains. For a tool with a notable idempotentHint=false on a read operation, some clarification would have been valuable.

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 no filler, which is appropriately sized for a simple getter. It is arguably under-specified rather than verbose, but there is no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a fully documented schema, an output schema, and annotations, so the description does not need to explain return values or parameters. Still, given the cluster/domain/route hierarchy and the presence of list/create/update/delete siblings, a sentence on scope and relationship would have made it complete.

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 all three identifiers (cluster_id, domain_id, route_id) are already documented in the schema. The description does not add any meaning, such as the relationship or hierarchy between cluster, domain, and route, so it sits at the baseline.

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

Purpose3/5

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

The description names a verb ('Get') and a resource ('a single realm route on a custom domain'), and 'single' distinguishes it from a list operation. However, 'realm route' is unexplained jargon and the definition never says what a domain route actually is or how it differs from the sibling get_domain tool.

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?

There is no guidance on when to use this versus skycloak_list_domain_routes (which would return many), skycloak_get_domain (parent resource), or the create/update/delete route siblings. The agent must infer that 'single' implies fetching one existing route by ID.

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