Skip to main content
Glama

Plan a server and get its checkout link

plan_server
Read-onlyIdempotent

Picks the edition, server type, plan and region for a game from what the person wants (how many players, mods or not), with the real price, and makes a checkout link on app.wilderack.com. The person opens the link, signs in or makes an account, checks everything and pays there; the server starts once it is paid. No account needed, and nothing is charged by this tool. Only games that are for sale get a link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game": "<game>"
    },
    "name": "plan_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesA game name or id, such as "minecraft", "terraria" or "factorio".
nameNoThe server's name, if the person said one.
planNoA plan id to use as is, such as ram-6g, instead of the suggested one.
moddedNoTrue for mods or plugins, which need more memory. For Minecraft Java mods (not plugins), also set serverType: fabric, neoforge or forge.
periodNomonth, quarter (every 3 months, 10% less on plans that sleep), year (15% less on plans that sleep) or pass3d (a 3-day pass that never renews). Default month.
regionNoA region id from list_regions. Leave out to let the person pick at checkout.
editionNoAn edition id from get_game, such as "java" or "bedrock". Default: the main edition.
modpackNoA Modrinth modpack id or slug, for games that take modpacks.
playersNoHow many people play at once, at most.
currencyNousd (before tax), eur or gbp (VAT included). Default usd.
serverTypeNoA server type id from get_game, such as paper, fabric or forge. Default: the one Wilderack suggests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description resolves the obvious tension by stating 'nothing is charged by this tool' and 'No account needed,' clarifying that producing a checkout link is not a purchase. It further explains that the person pays on app.wilderack.com and the server starts only after payment, which is behavior no annotation conveys.

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 core action and the resulting link are front-loaded in the first sentence, with the payment flow and constraints following. It is a dense block rather than a list, and the payment-flow sentence is long, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter planning tool with no output schema, the description covers what is returned (a checkout link), what is not done (no charge, no account), and the post-link flow. It does not describe the shape of the response beyond the link, such as whether the chosen plan and price are echoed back.

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, but the description adds meaning by mapping natural-language intent (how many players, mods or not) onto the players/modded/plan/region selection logic. It does not add per-parameter detail beyond what the schema already documents.

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 description names a specific action and outcome: it selects edition, server type, plan and region, prices it, and produces a checkout link on app.wilderack.com. That is clearly distinct from the sibling lookup tools (get_game, get_prices, list_regions), though it never explicitly contrasts itself with them.

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?

It states the triggering situation (a person wants a server, described by player count and mods) and the downstream flow after the link is returned. It also flags the exclusion 'Only games that are for sale get a link.' It stops short of naming an alternative tool or saying when not to plan at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources