Skip to main content
Glama
dwin-gharibi

ArvanCloud MCP Server

by dwin-gharibi

arvan_create_server

Provision one or more cloud servers with custom flavor, OS image, region, disk size, networking, security groups, SSH keys, and startup scripts.

Instructions

Create one or more cloud servers.

Args: name: Server name (a numeric suffix is added when count > 1). flavor_id: Plan/flavor id — see arvan_list_plans. image_id: OS/snapshot image id — see arvan_list_images. region: Region code; defaults to ARVAN_DEFAULT_REGION. disk_size: Root disk size in GB. count: How many identical servers to create. network_ids: Private network ids to attach. security_group_names: Security groups to apply. ssh_key_name: Name of an SSH key to inject (see arvan_list_ssh_keys). init_script: Cloud-init / startup script. ha_enabled: Enable high availability. create_type: Optional create type (e.g. image, snapshot). extra: Any additional fields to merge into the request body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
flavor_idYes
image_idYes
regionNo
disk_sizeNo
countNo
network_idsNo
security_group_namesNo
ssh_key_nameNo
init_scriptNo
ha_enabledNo
create_typeNo
extraNo
Behavior3/5

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

Annotations indicate it is not readonly and not idempotent, but the description adds no further behavioral details beyond creation. It does not contradict annotations.

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 front-loaded with the purpose and structured as a clear list of parameters. Every sentence adds value, and the length is appropriate for the parameter count.

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 (13 parameters, no output schema), the description covers parameters well but omits expected return values or failure behavior. It is adequate but not fully complete for an agent.

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?

Schema description coverage is 0%, so the description compensates well. Each parameter is explained briefly, with cross-references to related tools (e.g., arvan_list_plans) and specific behaviors (e.g., numeric suffix for name when count>1). Some parameters like 'extra' are vague.

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 'Create one or more cloud servers' with a specific verb and resource. It distinguishes from sibling tools like arvan_provision_server by focusing on initial creation. The mention of 'one or more' directly references the count parameter.

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 explicit guidance on when to use this tool versus alternatives like arvan_provision_server or arvan_rebuild_server. It references other tools for listing plans/images/ssh keys but does not define usage context or exclusions.

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/dwin-gharibi/arvancloud-mcp'

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