Skip to main content
Glama
Sign In
@easynodexyz/mcp-x402

@easynodexyz/mcp-x402

by easynodexyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_custom_name

Update or set a custom label for a VPS or Node instance, making instances easier to identify and manage.

Instructions

Set or update the custom name of a VPS or Node instance. Useful for labeling instances with friendly names.

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": {
      "instanceId": "<instanceId>",
      "type": "<type>",
      "customName": "<customName>"
    },
    "name": "update_custom_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesInstance type: "node" or "vps"
customNameYesCustom name for the instance (max 100 characters)
instanceIdYesInstance ID (userNode or userVps ID) to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Set or update' which implies mutation, but does not disclose permissions, reversibility, side effects, or response behavior. This is a significant gap for a mutation tool.

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 two concise sentences, the first stating the action and the second giving the purpose. Every word contributes value with no redundancy or filler.

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 simple 3-parameter mutation tool with complete schema coverage and no output schema, the description adequately covers purpose and parameters. Behavioral detail is lacking, but the tool is straightforward, so completeness is acceptable.

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%, with all three parameters clearly described. The description adds no extra semantic 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 clearly states 'Set or update the custom name of a VPS or Node instance' with a specific verb and resource, and it distinguishes this tool from sibling tools like list_instances or renew_instance by focusing on the labeling action.

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 phrase 'Useful for labeling instances with friendly names' provides clear context for when to use the tool. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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