Scaleway MCP Server

list_k8s_clusters

List all Kubernetes clusters in a Scaleway region, optionally specifying a region to filter; falls back to default region.

Instructions

List all Kubernetes clusters in a Scaleway region.

Args: region: Scaleway region (e.g., fr-par, nl-ams). If not provided, uses default region.

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": "list_k8s_clusters"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No

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

Behavior3/5

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

No annotations are provided, so the description carries the burden of disclosing behavior. It discloses the default region behavior, which is useful, but it does not explicitly mention that the operation is read-only/safe, nor does it address pagination or authentication. The non-destructive nature is implied by 'List', but not stated.

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 extremely concise: a single functional sentence plus a one-line param explanation. It front-loads the purpose and wastes no words, making it easy to scan and understand.

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?

Given the tool's simplicity (one optional parameter, output schema exists) and the presence of an output schema, the description covers the essential behavior. It could mention pagination or relationship to 'get_k8s_cluster', but these are not critical for a basic list operation. Overall, adequate for the context.

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 schema only declares 'region' as a string/null with a default, but the description adds meaning by giving example values ('fr-par', 'nl-ams') and explaining behavior when omitted. This compensates for the 0% schema description coverage and clarifies the parameter's purpose.

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 the operation ('List'), the resource ('Kubernetes clusters'), and the scope ('in a Scaleway region'). It distinguishes itself from sibling 'get_k8s_cluster' by indicating 'all' clusters rather than a single one.

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 by saying 'List all', but it does not explicitly name alternatives like 'get_k8s_cluster' for retrieving a single cluster. It provides helpful context about the region parameter (default behavior), but no exclusion or when-not-to-use guidance.

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

Deploy Server