Skip to main content
Glama
Sign In
VPSnet

VPSnet

by bacarrdy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Quote public address renewal

quote_public_address_renewal

Quote the renewal cost for an owned public IP address without charging, returning a quote and idempotency key needed to confirm the selected term.

Instructions

Quote the address's selected term (one month when omitted) without charging; use the returned quote and this key for confirmation. 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
address_idYesExact 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.2/5.0
Behavior5/5

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

Goes far beyond the annotations: required scopes (networking:read vs networking:manage), the fact that full/read defaults do not grant networking, backend ownership/feature/2FA enforcement, spend caps and paid-operation enablement, and that the call does not charge. It also explains that an accepted operation is pending rather than proof of connectivity, and precisely how in_progress/reason_kind/reason_code should be interpreted during polling — none of which is in the annotations.

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

Conciseness3/5

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

The purpose is front-loaded, but the remainder is a dense run-on of semicolon-chained requirements (auth, 2FA, polling semantics, idempotency, spend caps, payment method) that is hard to parse and mixes procedural steps with invariants. Several sentences would earn their place better as separate, ordered statements.

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 3-parameter, non-read-only, open-world tool with no output schema, the description supplies the pricing unit (gross_amount EUR), the operation/resource polling model with timing advice (next_check_seconds), failure classification, and the confirmation prerequisite. An agent has everything needed to quote, wait, and hand off to confirmation 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 100%, so the baseline is 3; the description still adds real meaning by stating the same Idempotency-Key must be reused for confirmation, that preserving the exact quote matters, and that gross_amount in EUR must be disclosed before approval. It does not add much about address_id beyond the schema's own 'returned by an owned networking resource' note.

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 first clause names a specific verb and resource (quoting a public address's selected term) and states the zero-charge default plus the one-month default. It never explicitly contrasts itself with the near-named siblings quote_network_public_address, quote_network_product_renewal, or renew_network_public_address, so an agent must infer that this is the renewal-quote step of a quote→confirm workflow rather than a new purchase.

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?

Strong sequencing guidance: read capabilities and owned resource state first, obtain approval for the exact change, then use the returned quote and the same key for confirmation. It also sets clear exclusions around retries ('never automatically retry') and payment methods. It stops short of naming an alternative sibling tool or stating when this should be skipped in favor of renew_network_public_address.

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