Skip to main content
Glama
bacarrdy

VPSnet

by bacarrdy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get networking operation

get_networking_operation
Read-onlyIdempotent

Read an accepted network or port operation to check its progress, outcome, or failure; poll while in_progress and wait next_check_seconds between reads.

Instructions

Read an accepted network or port operation only. Poll on in_progress (true until succeeded, failed or cancelled) and wait next_check_seconds between reads; reason_kind says what reason_code is: waiting (progress, including queued, pending and control-plane-not-yet-answered reasons - not an error), failure or outcome. A port reserve (the operation an attach returns) names its activation_operation_id once the activation that finishes the attachment exists; the completed history line names both ids. A successful network_graph_created operation permits checking network.port_intent_ready for the first attachment; it does not prove guest connectivity. Security-policy, appliance and public-binding operation IDs belong to different stores. Poll security policies with get_network_security_policy, appliances with get_network_appliance_operation, public bindings with get_network_public_binding, and DNS changes through get_private_network.settings.dns_change. Requires explicit networking:read for reads or networking:manage for changes; full/read defaults do not grant networking. The backend enforces ownership, feature availability and service 2FA locks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_idYesExact lowercase UUID returned by an owned networking resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.16

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it explains that in_progress stays true until succeeded/failed/cancelled, documents reason_kind semantics (waiting vs failure vs outcome, queued/pending not an error), describes the activation_operation_id relationship for port reserves, and states auth requirements plus backend enforcement of ownership, feature availability and 2FA locks.

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?

Front-loaded with the core read purpose and polling cadence, then routing and semantics. Every sentence carries information, though the density is high and the sibling enumeration in the middle is somewhat list-like; it is long but not padded.

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?

With no output schema, the description carries the full burden and does so: it explains the returned in_progress/reason_kind/next_check_seconds fields, the semantics of a successful network_graph_created (and its limits re: guest connectivity), and the permission model. Nothing an agent needs to invoke and interpret this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the operation_id format is fully documented there, so baseline is 3. The description adds real meaning by constraining which operation IDs are valid here (network/port operations only, not security-policy/appliance/public-binding/DNS stores), clarifying the ID's provenance beyond the schema's generic phrasing.

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?

States a specific verb and resource ('Read an accepted network or port operation') and immediately scopes it with 'only'. It explicitly distinguishes its resource domain from sibling stores (security-policy, appliance, public-binding operation IDs), so an agent can route without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit polling guidance ('poll on in_progress... wait next_check_seconds between reads') and names the exact alternatives for other operation types: get_network_security_policy, get_network_appliance_operation, get_network_public_binding, and get_private_network for DNS. This is when/when-not plus alternatives, fully specified.

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