Skip to main content
Glama
spron-in

mcp-everest

by spron-in

create_database_cluster

Create a new database cluster by specifying namespace, name, engine type, and resource limits. Configure storage, replicas, CPU, memory, and proxy replicas for scalable database deployments.

Instructions

Create a new database cluster in the specified namespace.

Args:
    namespace: The namespace to create the cluster in
    name: Name of the database cluster
    engine_type: Type of database engine (e.g. 'pxc')
    storage_size: Size of storage using the Mi, Gi suffix
    replicas: Number of database replicas
    cpu: CPU cores per replica
    memory: Memory per replica using the Mi, Gi suffix
    allow_unsafe: Allow unsafe configurations
    proxy_replicas: Number of proxy replicas

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpuNo
nameYes
memoryNo1Gi
replicasNo
namespaceYes
engine_typeYes
allow_unsafeNo
storage_sizeNo10Gi
proxy_replicasNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It confirms mutation ('create') but does not disclose potential side effects, auth requirements, idempotency, failure behavior, or any constraints beyond parameter descriptions.

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?

The description is front-loaded with the main purpose, followed by a clear list of parameter descriptions. It is appropriately sized for a tool with 9 parameters, but could be slightly more concise by grouping optional defaults.

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?

Given the complexity (9 parameters, no output schema), the description covers parameter meanings fully but lacks details about the return value, asynchronous behavior, or validation rules. It is minimally adequate for a creation tool.

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?

With schema description coverage at 0%, the description compensates by providing meaningful explanations for each parameter, e.g., 'storage_size: Size of storage using the Mi, Gi suffix' and 'cpu: CPU cores per replica'. This adds significant value beyond the schema's type and default.

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 starts with 'Create a new database cluster in the specified namespace,' clearly stating the verb (create) and resource (database cluster). It distinguishes from sibling tools like get_database_cluster and list_database_clusters, which are read-only.

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 this is for creation, but provides no explicit guidance on when to use this tool versus alternatives, such as when to use editing tools. It lacks when-not-to-use or prerequisite conditions.

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/spron-in/mcp-everest'

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