Scaleway MCP Server

get_k8s_cluster

Retrieve detailed status and configuration for a Kubernetes cluster by its ID and optional region.

Instructions

Get detailed information about a Kubernetes cluster.

Args: cluster_id: The ID of the cluster to retrieve region: Scaleway region (e.g., fr-par, nl-ams). If not provided, uses default region.

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>"
    },
    "name": "get_k8s_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No
`cluster_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the transparency burden. It only says 'detailed information' without disclosing the read-only nature, potential error conditions, or any side effects, leaving significant gaps.

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?

The description is concise and front-loaded, using a standard Args structure with no filler or redundancy. Every sentence adds value.

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 simple getter, the description covers the essential parameters and default region behavior. The output schema exists to document return values, so that is not a gap. However, it lacks any mention of errors or prerequisites.

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 description clarifies 'cluster_id' and gives concrete examples and default behavior for 'region', which the schema leaves unspecified. This adds meaningful meaning beyond the bare field names.

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?

The description clearly states a specific verb ('Get') and resource ('Kubernetes cluster'), narrowing to 'detailed information.' It naturally distinguishes from sibling 'list_k8s_clusters' by focusing on a single cluster.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear: this tool retrieves a specific cluster by ID, and the region default is explained. However, it does not explicitly contrast with list_k8s_clusters or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server