Skip to main content
Glama
madmickstar

mcp-eveng

by madmickstar

change_node_delay

Change a single node's startup delay or apply incremental delays to multiple nodes in an EVE-NG lab, with an explicit confirmation step before any changes take effect.

Instructions

Change a node's startup delay (seconds before it auto-starts), one node or in bulk.

node_id always means single-node mode, regardless of bulk: sets that one node's delay to delay (default 10).

Otherwise bulk=true is required, in one of two forms:

  • names given (a name, or list of names -- case-insensitive substring match against every node's name): every match gets an incrementing delay (increment, default 10) -- the first matched node gets increment seconds, the second increment*2, and so on, in the order the names were given.

  • names omitted: lists every node in the lab with its current delay (status "selection_required") and asks for order -- the list numbers, in the sequence you want increasing delays applied (e.g. "3,1,2"); node 3 gets increment seconds, node 1 gets increment*2, node 2 gets increment*3.

Every mode ends the same way: one more explicit confirmation summarizing every node and its new delay, warning that each will be stopped first (required regardless of PRO/Community, same as edit_lab_node). Reply "accept" or "yes" (confirm) to apply; anything else cancels. Nothing is stopped or changed before that.

Args: lab_path: Full path to the .unl lab file. node_id: Id of a single node to change. Overrides bulk if given. delay: New delay in seconds, for single-node mode. Default 10. bulk: Required (with node_id omitted) for multi-node mode. names: Node name or list of names to match (case-insensitive substring), for bulk mode. Omit to be shown every node and asked for order instead. increment: Delay increment in seconds between successive nodes, for bulk mode. Default 10. order: When bulk mode listed every node, the numbers from that list in the sequence you want increasing delays applied. confirm: Set true on the final call to actually apply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bulkNo
delayNo
namesNo
orderNo
confirmNo
node_idNo
lab_pathYes
incrementNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description bears full responsibility, and it excels. It discloses that nodes will be stopped before the change, that the operation requires explicit confirmation, and explains the incrementing-delay logic in bulk mode. No behavioral surprises are left unaddressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with an overview, mode breakdown, and Args list. It is somewhat verbose (repetition of defaults like 'default 10'), but the complexity of the tool (two modes, confirmation workflow) justifies the length. It is front-loaded with the core purpose.

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

Completeness5/5

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

Given 8 parameters, no annotations, and an output schema that isn't described (but exists), the description covers all behavioral aspects: confirmation flow, node-stopping, default values, and both single and bulk modes. The tool's interaction model is fully documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully compensate. It does so with a detailed Args section covering all 8 parameters, their defaults, relationships (e.g., node_id overrides bulk), and usage patterns. Each parameter's meaning is clearly explained beyond the schema's bare types.

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 the tool's purpose: 'Change a node's startup delay'. It explains single-node and bulk modes, making the verb-resource relationship explicit. While siblings like 'edit_lab_node' exist, this tool's specific focus on delay distinguishes it adequately.

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 provides clear guidance on when to use each mode (node_id vs bulk, names vs order) and describes the required confirmation step. It does not explicitly compare to sibling tools like 'edit_lab_node', but the instructions are sufficient for correct invocation in most cases.

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/madmickstar/mcp_eveng'

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