Skip to main content
Glama

Plans and prices

get_prices
Read-onlyIdempotent

Wilderack's plans with their real prices for each period, the first-order offer and what they renew at. Every plan runs any game whose minimum fits. No account needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoOne plan id, such as ram-4g. Leave out for every plan.
currencyNousd (before tax), eur or gbp (VAT included). Default usd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: first-order versus renewal pricing, that every plan supports any game meeting its minimum spec, and that no account/authentication is required to view prices.

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?

Three short sentences, front-loaded with what is returned and followed by two useful qualifiers. No filler, though the game-compatibility sentence is somewhat tangential to a pricing lookup.

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?

With no output schema, the description does a reasonable job of previewing the return shape (per-period prices, first-order offer, renewal price) for a two-parameter, fully documented, read-only tool. An agent has enough to call it and interpret the response, though the exact result structure is not spelled out.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the plan parameter explaining omission means all plans and the currency parameter explaining tax treatment and default. The description adds nothing parameter-specific beyond the schema, so the baseline of 3 applies.

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 resource and contents: "Wilderack's plans with their real prices for each period, the first-order offer and what they renew at," so an agent knows this returns pricing data including promotional and renewal rates. It is clearly distinct from siblings like get_game or list_regions, though it never uses an explicit verb like "list" or "returns."

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the pricing detail and "No account needed" suggest this is the pre-purchase lookup step, and the note about plans running games hints at a relationship with plan_server/get_game. There is no explicit statement of when to call this versus plan_server or find_games, and no stated exclusions.

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