Skip to main content
Glama

nodes_bulk_update

Bulk update selected nodes' properties—tags, notes, country codes, and consumption multipliers—by providing their UUIDs.

Instructions

Bulk update properties for selected nodes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoFree-form note (max 255 chars, null to clear)
tagsNoTags (uppercase letters, numbers, underscores, colons; max 36 chars each, up to 10)
uuidsYesArray of node UUIDs to update
countryCodeNoNew country code
consumptionMultiplierNoNew consumption multiplier (0.0–100.0)
nodeConsumptionMultiplierNoNew per-node consumption multiplier (0.0–100.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.9/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 behavioral burden. It signals mutation via 'update' but does not disclose partial-update semantics, whether the same properties apply to all selected nodes, validation or failure behavior, or permissions. This is a significant gap for a bulk mutating tool.

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 a single front-loaded sentence with no filler, making it easy to parse. It is slightly under-sized for a 6-parameter bulk mutation tool, but the conciseness itself is strong.

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?

The schema covers parameter formats, but the description omits essential operational semantics: how bulk selection works, whether omitted properties are left unchanged, what happens on invalid UUIDs, and what the call returns. With no annotations and no output schema, this is not complete enough for confident invocation.

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%, so all six parameters are already documented with types and constraints. The description adds no parameter-specific meaning beyond the generic word 'properties', which is acceptable at the baseline given the complete schema coverage.

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 states a specific verb ('bulk update') and resource ('nodes') and implies multi-node selection via 'selected nodes', which clearly conveys the core operation. However, 'properties' is generic, and the description does not differentiate this tool from similar bulk siblings like nodes_bulk_profile_modification or nodes_bulk_actions.

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?

There is no guidance on when to use this tool instead of alternatives such as nodes_update, nodes_bulk_profile_modification, or nodes_bulk_actions. It does not state prerequisites, exclusions, or conditions for preferring one sibling over another.

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