Skip to main content
Glama
bacarrdy

VPSnet

by bacarrdy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Configure application access

configure_application_access
DestructiveIdempotent

Queue an access change for one owned VPSnet managed application, setting each endpoint to private, public HTTP, managed HTTPS, platform HTTPS, or external HTTPS after confirmation.

Instructions

Queue an access change for one owned managed application. Read get_application_installation first and pass its current revision. If access.request.schema_version=2, preserve every exact endpoint key and configure each endpoint independently; use service and port metadata to match the user's intent instead of prioritizing array order or primary=true. Private removes that route's public listener. Public HTTP exposes it through the server public IP. Managed HTTPS requires an eligible VPSnet-managed DNS zone, subdomain, and explicit DNS approval; it may also carry additional_addresses (up to 4 per endpoint, 8 per application): other names in the customer's own VPSnet zones, each with its own DNS approval, where name '' or '@' is the zone's bare domain (for example example.com next to www.example.com) and action 'redirect' (default) answers 301 to the main address keeping path and query while 'serve' opens the same application; the main address is never changed by adding or removing an additional address; the list is the complete wanted set, so an access change that omits additional_addresses removes the saved ones (pass them again to keep them); additional_addresses are refused on every other mode. External HTTPS only records the customer-managed URL; VPSnet does not configure or validate its DNS, TLS, or reverse proxy. Confirm the exact change with the user first. A queued response must be verified with get_application_installation and get_application_events. Requires applications:manage and is not a paid API-key operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessYesOne access choice, or schema_version=2 with every exact endpoint key and its independent access choice
orderNoYesTenant-owned service order number: 1-64 ASCII letters, digits or hyphens, e.g. VP12345 or VP12345-1
confirmedYesTrue only after the user confirmed this access change
idempotencyKeyYesClient-global unique key. Reuse it only to replay this exact access request; never reuse it for another service or request.
installation_idYesManaged application installation UUID
expected_revisionYesCurrent installation revision returned by get_application_installation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.16

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructive, idempotent, and open-world, but the description adds substantial context beyond them: the operation is queued/asynchronous and must be verified, private mode removes a public listener, additional_addresses are refused on all other modes and are treated as the complete wanted set (omitting them deletes saved entries), external_https is not validated by VPSnet, and it requires applications:manage and is not a paid API-key op.

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 action and prerequisite, and dense with useful detail, but it is delivered as one long semicolon-chained paragraph that is harder to parse than necessary. Little is wasted, yet a bulleted breakdown of modes would improve scannability.

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?

No output schema exists, and the description compensates by naming the verification tools and describing every mode's behavior in depth. Given a fully documented nested schema and complete annotations, nothing an agent needs to call this correctly is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds real business meaning: it explains the schema_version=2 per-endpoint model, the redirect (301, keeps path/query) vs serve distinction for additional_addresses, the '@'/'' bare-domain convention, and the max-address constraints — all beyond what the raw schema conveys.

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 — 'Queue an access change for one owned managed application' — and immediately distinguishes itself from read siblings by naming get_application_installation as a prerequisite rather than an alternative. An agent can tell this is the write-side counterpart to the application inspection tools.

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?

Explicitly sequences the workflow: read get_application_installation first, pass its revision, confirm with the user, then verify the queued result with get_application_installation and get_application_events. It also tells the agent how to disambiguate endpoint intent (use service/port metadata instead of array order or primary=true).

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