Skip to main content
Glama

List playground plans

list_playground_plans
Read-only

List the orderable Ankra Playground sizes with their fixed monthly prices, whether the shared pool could place each size right now, the organisation's playground memory budget and headroom, and whether the organisation holds the paid billing plan and payment card that paid sizes require. Call this before create_playground or resize_playground: it names the valid size ids, and a size marked unavailable or over budget will be refused by the order. When a size does not fit the memory budget, offer request_limit_increase instead of retrying. Pass cluster_id (or run it from the playground's conversation) for a playground that runs on Ankra Cloud: the answer then carries 'resize' with the Ankra Cloud plans that playground can move to (their ids are the sizes resize_playground takes), each plan's monthly price, whether it can be resized now and why not (a free trial keeps its size until a payment method is added), and restart_notice, the sentence to tell the user before proposing the resize.

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": "list_playground_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of a playground cluster to also list resize options for. Optional; the conversation's cluster is used when it is a playground.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cluster_id
      Added value: +{
      +  "description": "UUID of a playground cluster to also list resize options for. Optional; the conversation's cluster is used when it is a playground.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, and the description adds real behavioural context on top: sizes can be marked unavailable or over budget and orders for them will be refused, free trials keep their size until a payment method is added, and a restart_notice sentence must be shown before proposing a resize. It stops short of describing pagination, caching/staleness of the shared-pool availability check, or any permission requirements for reading billing state.

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-loads the core purpose and then moves to preconditions and alternatives in a logical order, with no filler sentences. It is dense to the point of being two very long clauses chained with commas, and the billing/payment-card condition is stated twice (once for sizes, once for trials), which slightly costs readability.

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?

There is no output schema, so the description carries the full burden of describing the return payload, and it does: per-size price and availability, budget headroom, billing standing, plus the optional 'resize' block with per-plan price, resize eligibility and reason, and restart_notice. For a single-optional-parameter read tool this is complete enough to call correctly without further exploration.

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 coverage is 100% and the schema already documents cluster_id as an optional playground cluster UUID with conversation fallback, so the description mostly restates that. It does add one piece of meaning beyond the schema: passing it makes the response carry a 'resize' block whose plan ids are the values resize_playground accepts, which tells the agent why to supply it rather than just what it is.

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 concrete verb and resource (list orderable Playground sizes) and enumerates exactly what each entry carries: monthly price, current placement availability, memory budget/headroom, and billing/payment-card status. It is unmistakable against siblings like get_playground_status or list_instance_types because it frames the output as the orderable size catalogue.

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?

Gives explicit sequencing ('call this before create_playground or resize_playground'), explains why (it names the valid size ids and the order will refuse unavailable/over-budget sizes), and redirects to a named alternative (request_limit_increase) instead of retrying when the budget does not fit. It also states the condition for passing cluster_id (Ankra Cloud playgrounds) versus relying on the conversation context.

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.