Skip to main content
Glama

Set VPS label

vps_set_label
Idempotent

Rename a VPS (changes the local display name only).

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": {
      "id": "<id>",
      "name": "<name>"
    },
    "name": "vps_set_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
nameYesNew display name (1-32 characters)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the change affects only the local display name and not any remote/host configuration. It stops short of stating permissions or whether the caller must own the VPS.

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?

One short sentence with the action front-loaded and the constraining scope in parentheses. Nothing is redundant and nothing important is buried.

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

Completeness4/5

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

For a two-parameter, fully documented mutation with annotations and no output schema, the description supplies what an agent needs: what changes and how narrowly. Only minor gaps remain, such as whether the new label is applied immediately or requires a subsequent read.

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%: id is documented as the VPS ID with a 24-hex pattern and name as a 1-32 character display name. The description reinforces that 'name' is a display label rather than a hostname, which is a small but real addition; otherwise the schema carries the load, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Rename') and resource ('a VPS') and adds a scope clarification that it only changes the local display name. That parenthetical meaningfully distinguishes this from remote-configuration siblings like vps_set_ssh_banner or vps_set_password_auth, though it does not explicitly name any alternative.

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?

Usage is implied: use it to change a VPS's display label. There is no explicit when-to-use versus when-not, no mention of prerequisites such as the VPS existing, and no reference to sibling tools such as webspace_set_label or vps_create. Adequate but leaves routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.