Skip to main content
Glama

Create playground

create_playground
Destructive

Order a new Ankra Playground environment - a ready-in-minutes hosted Kubernetes namespace on Ankra's shared pool - at a named size from list_playground_plans. Omitting size orders the free trial, which is limited to one per organisation and needs no billing setup. Paid sizes are billed monthly pro-rata from the moment the environment is ready, and are refused unless the caller holds billing permissions and the organisation has a paid billing plan, a payment card on file, no long-overdue invoices, and headroom in its playground memory budget - list_playground_plans reports all of that up front, and a refusal names the missing piece. Returns the new cluster id; poll get_playground_status until the phase reaches ready.

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

Input Schema

NameRequiredDescriptionDefault
sizeNoPlan id from list_playground_plans (for example trial, small, medium, large, xlarge). Omit to order the free trial.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: trial is limited to one per organisation with no billing setup, paid sizes bill monthly pro-rata from readiness, and creation is refused unless billing permissions, a paid plan, a card on file, no over-due invoices, and memory-budget headroom all hold. It also notes that a refusal names the missing piece, which tells the agent how to interpret failure.

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 tightly structured across three sentences with no filler. The enumeration of five paid-tier prerequisites is somewhat heavy given the description itself says list_playground_plans reports all of that up front, which borders on redundancy.

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, and the description compensates by stating the return value ('Returns the new cluster id') and the required follow-up ('poll get_playground_status until the phase reaches ready'). For a single-optional-parameter creation tool, nothing an agent needs in order to call it correctly is missing.

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% and the schema already explains that omitting size yields the free trial, so the baseline is 3. The description adds genuine meaning on top: the trial's one-per-organisation limit, the absence of billing setup for it, and the pro-rata billing consequence of choosing a paid size.

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 ('Order a new Ankra Playground environment') and immediately characterizes what that is ('a ready-in-minutes hosted Kubernetes namespace on Ankra's shared pool'), which separates it from generic cluster-creation siblings like create_managed_cluster or create_aws_cluster.

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?

Explicitly routes the agent to list_playground_plans for plan selection and eligibility, and to get_playground_status for polling after the call. The omission path ('Omitting size orders the free trial') is spelled out. It stops short of stating when NOT to use this tool (e.g. use resize_playground for an existing environment), so not quite a 5.

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.