Skip to main content
Glama
Sign In
timeweb-mcp-server

timeweb-mcp-server

by webkoth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

timeweb_create_image

Create a custom OS image from a server disk snapshot, enabling reusable templates for consistent server deployments.

Instructions

Create a custom OS image from a server disk (snapshot)

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": {
      "disk_id": "<disk_id>",
      "name": "<name>"
    },
    "name": "timeweb_create_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesImage name
formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readable
disk_idYesServer disk ID to create image from
descriptionNoImage description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 disclose behavior independently. It only names the action without explaining side effects, prerequisites, permissions, or whether the source disk is affected. This is a significant gap for a mutating create operation.

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 a single sentence that front-loads the purpose with no redundant words or fluff, making it immediately clear and efficient.

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?

The schema fully documents parameters, but with no output schema, the description doesn't explain return values or operation progress. It also lacks notes on prerequisites or whether the operation is asynchronous, though the simple nature of the create action partially mitigates this.

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?

All four parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds only the source context for disk_id but no additional meaning for name, format, or description beyond what the schema already states.

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?

Clearly states the action 'Create' and resource 'custom OS image' along with the source 'server disk (snapshot)', which is specific and distinguishes it from sibling tools like delete_image, get_image, or create_server.

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 description implies its use for creating an OS image from a disk, providing clear context. However, it does not explicitly mention when to use this tool over alternatives like create_server_disk or update_image, nor does it state exclusions.

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

Deploy Server

Other Tools