Skip to main content
Glama

databases_create_instance

Create a Managed Database instance on Scaleway. Specify engine, user credentials, and node type to provision a scalable database with optional high availability and custom storage.

Instructions

Create a Managed Database instance.

The instance is tagged created_by=scaleway-mcp so it can later be identified and safely deleted by this server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional instance name (a random one is generated if omitted).
tagsNoOptional additional tags.
engineYesDatabase engine version, e.g. ``PostgreSQL-15`` or ``MySQL-8``.
regionNoRegion. Defaults to the configured region.
passwordYesPassword for the initial admin user.
node_typeYesNode type, e.g. ``DB-DEV-S`` or ``DB-GP-XS``.
user_nameYesName of the initial admin user to create.
project_idNoOptional project ID. Defaults to the configured project.
volume_sizeNoBlock storage volume size in bytes (default 5 GB).
is_ha_clusterNoWhether to provision a high-availability cluster.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

Description only discloses the tagging behavior. Without annotations, it fails to mention side effects (cost, irreversibility), idempotency, permissions, or what happens on duplicate attempts.

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?

Two sentences, front-loaded with purpose. Slightly more verbose due to tagging detail, but still efficient.

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

Completeness2/5

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

Despite an output schema and 10 parameters, the description omits lifecycle details, default name format, initial database, and relationship to other database tools. The tagging note is helpful but insufficient.

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 coverage is 100%, so baseline is 3. The description adds no extra parameter meaning beyond what the schema already provides.

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 states 'Create a Managed Database instance' with clear verb and resource. It also mentions the tagging behavior, which helps distinguish it from sibling tools like databases_list_instances or databases_create_backup.

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?

No guidance on when to use this tool vs alternatives (e.g., redis_create_cluster, kubernetes_create_cluster). No prerequisites, exclusions, or typical scenarios are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sndpl/scaleway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server