Skip to main content
Glama
Sign In
VPSnet

VPSnet

by bacarrdy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Quote network public address

quote_network_public_address

Quotes a paid public network address for checkout without charging, optionally preflighting attachment limits for a network before payment.

Instructions

Quote a new paid public address for common checkout; no charge. Optional network_id preflights attachment limits before payment. Always prepare_after_payment=true; confirm through order_network_product with matching target if attaching. 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. Read current capabilities and owned resource state first; obtain approval for the exact change. An accepted operation is pending, not proof of connectivity. Poll the returned operation/resource on its in_progress flag, waiting next_check_seconds between reads: while in_progress is true its reason_code is what is awaited (reason_kind waiting, e.g. a queued or pending reason, or a control plane that has not answered yet), never an error; only in_progress false with reason_kind failure is a failure. Preserve reason_code. On transport uncertainty inspect state and reuse only the original key and unchanged request; never automatically retry. Requires full API access, networking:manage, enabled paid operations, networking:order and spend caps. Choose a supported live catalog tier and its documented request kind; preserve the exact quote; disclose its gross_amount in EUR before user approval. The same Idempotency-Key is required for quote and confirmation. API-key checkout supports the advertised account-balance payment method only. Payment acceptance is not resource readiness.

Input Schema

NameRequiredDescriptionDefault
network_idNoExact lowercase UUID returned by an owned networking resource
period_monthsNoPaid term in months from the current list_network_products catalog; omit for one month. The 1-120 bound is not an offer list. Disclose this term and the exact quoted total before confirmation.
idempotencyKeyYesStable Idempotency-Key for this exact intent; reuse unchanged on recovery, never generate a new key for an uncertain result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.20
    • addedInput schema / properties / period_months
      Added value: +{
+  "description": "Paid term in months from the current list_network_products catalog; omit for one month. The 1-120 bound is not an offer list. Disclose this term and the exact quoted total before confirmation.",
+  "maximum": 120,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv2.3.16

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the quote is free but creates a pending operation, that backend ownership and feature checks apply, that payment acceptance is not readiness, and how to interpret in_progress versus reason_kind=failure. It also specifies idempotency-key recovery behavior and warns never to automatically retry on transport uncertainty.

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 purpose and no-charge constraint are front-loaded, and most of the dense text carries operational or safety-relevant guidance. It is long and somewhat run-on, but the complexity of the financial/networking workflow justifies most of the length.

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?

For a high-stakes quote operation with no output schema and sparse annotations, the description covers permissions, approval, quoted amount disclosure, idempotency, polling semantics, and failure interpretation. An agent has enough information to invoke it and handle its result correctly.

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 already 100%, so the schema documents all three parameters thoroughly. The description still adds useful meaning, especially that network_id preflights attachment limits and that the same Idempotency-Key must be used for quote and confirmation.

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 first sentence states a specific verb and resource: quote a new paid public address for checkout, with no charge. It also distinguishes the operation from confirmation by naming order_network_product and from renewal siblings by specifying a new public address.

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?

The description gives clear when-to-use guidance: quote first, disclose the EUR gross amount, obtain approval, then confirm through order_network_product with the matching target. It also names prerequisites, approval requirements, and the supported payment method, leaving little ambiguity about invocation context.

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