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

timeweb-mcp-server

by webkoth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

timeweb_unbind_floating_ip

Unbind a floating IP from its current resource to free it for reassignment or release.

Instructions

Unbind a floating IP from its current resource

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": {
      "floating_ip_id": "<floating_ip_id>"
    },
    "name": "timeweb_unbind_floating_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readable
floating_ip_idYesFloating IP ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and binds to a resource, but does not mention side effects, reversibility, permissions required, or what happens to the freed resource. For a mutation tool, this is insufficient.

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, front-loaded sentence that conveys the core action without waste. It is concise and to the point.

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?

As a mutation tool with no annotations and no output schema, the description is too minimal. It fails to explain the consequences of unbinding, when it should be used, or what the response will look like. The 100% schema coverage helps with parameters but not with broader operational context.

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 description coverage is 100% as both parameters (floating_ip_id and format) have descriptive text. The description adds no additional parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('Unbind') and resource ('floating IP') and adds context ('from its current resource'). It clearly distinguishes this from sibling operations like bind_floating_ip and delete_floating_ip.

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?

The description provides no guidance on when to use this tool versus alternatives such as bind_floating_ip or delete_floating_ip. It simply states the action without indicating prerequisites, exclusions, or alternative scenarios.

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