Skip to main content
Glama

create_tier1_gateway

Creates a Tier-1 gateway for routing segments, optionally linked to a Tier-0 for north-south connectivity. Set route advertisement types to enable external reachability of connected subnets.

Instructions

[WRITE] Create a Tier-1 gateway for routing segments, with optional Tier-0 uplink.

For north-south reachability, link it to a Tier-0 (get the path from list_tier0_gateways). Side effect to note: if route_advertisement is omitted, nothing is advertised to the Tier-0, so connected subnets stay unreachable from outside until advertisement types are set (here or via update_tier1_gateway). Re-running with the same tier1_id overwrites it (PUT semantics). Returns the created gateway dict; on failure returns {"error", "hint"}. Recorded in the audit log (~/.vmware/audit.db).

Args: tier1_id: Unique gateway identifier (alphanumerics, hyphens, underscores only); becomes policy path /infra/tier-1s/. display_name: Human-readable name shown in the NSX UI. tier0_path: Parent Tier-0 policy path, e.g. "/infra/tier-0s/". Omit to create a standalone (unlinked) gateway. edge_cluster_path: Edge cluster policy path for stateful services such as NAT, e.g. "/infra/sites/default/enforcement-points/default/ edge-clusters/". Optional. route_advertisement: Comma-separated advertisement types. Valid values: TIER1_CONNECTED, TIER1_STATIC_ROUTES, TIER1_NAT, TIER1_LB_VIP, TIER1_LB_SNAT, TIER1_DNS_FORWARDER_IP, TIER1_IPSEC_LOCAL_ENDPOINT. target: NSX Manager name from config.yaml. Uses the default target if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
tier1_idYes
tier0_pathNo
display_nameYes
edge_cluster_pathNo
route_advertisementNo
Behavior5/5

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

Discloses idempotent behavior (PUT semantics), audit logging, and side effects of omitted route_advertisement. No contradiction with annotations (readOnlyHint=false, destructiveHint=false).

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?

Well-structured with summary, body, and Args. Slightly long but every sentence adds value. Could be trimmed slightly but effective.

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?

Covers side effects, audit log, return value shape, and parameter details. No output schema, but description provides sufficient completeness for a complex creation tool.

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?

All 6 parameters are explained in the 'Args' section with constraints, examples, and valid values. Compensates for 0% schema coverage.

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?

Starts with '[WRITE] Create a Tier-1 gateway' – specific verb+resource. Distinguishes from siblings like update_tier1_gateway and delete_tier1_gateway.

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?

Provides explicit context: 'For north-south reachability, link it to a Tier-0' and warns about route_advertisement omission. Does not explicitly state when not to use, but guides effectively.

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/zw008/VMware-NSX'

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