Skip to main content
Glama

Create application

gameye_create_application

Create a Gameye application image with ports, TLS, resource limits, regions, and registry settings. Use dryRun to preview the API request before sending.

Instructions

Admin tool. Create a new application (an image Gameye can run). Set tls on a port here if you need it: it can only be set at creation, because gameye_edit_application drops it. Needs the application:write scope. Pass dryRun=true to preview the request. Needs GAMEYE_API_TOKEN; without one, returns setup steps and sends nothing.

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": {
      "name": "<name>",
      "registry": "<registry>",
      "repository": "<repository>",
      "tagKeep": "<tagKeep>",
      "networkMode": "<networkMode>",
      "limits": "<limits>",
      "reservation": "<reservation>",
      "nodePool": "<nodePool>",
      "regions": "<regions>",
      "ports": "<ports>"
    },
    "name": "gameye_create_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesApplication name; also the image name used when launching sessions
portsYesContainer ports to expose
dryRunNoReturn the exact request that would be sent, with the API token masked, and send nothing
limitsYes
regionsYesRegion names (see gameye_list_regions)
tagKeepYesHow many image tags Gameye keeps for this application
nodePoolYesNode pool name
registryYesName of a Gameye image registry, e.g. 'dockerhub' or 'ghcr'. The server looks the name up and returns 404 if it is unknown; gameye_list_applications shows the names your applications use
repositoryYesImage repository in that registry, without a tag
networkModeYesContainer network mode
reservationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already disclose non-read-only, non-idempotent, open-world behavior, and the description adds genuinely useful context on auth scope, the token-missing dry behavior ("returns setup steps and sends nothing"), and the irreversible TLS-at-creation semantics. However, it does not say what a successful call returns or whether the new application's identifier is surfaced, which matters for a creation tool.

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?

Four dense sentences, front-loaded with purpose and then constraints, with no filler. Slight crowding of auth, dry-run, and TLS caveats into one paragraph costs it a point but nothing is wasted.

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 nested creation tool with no output schema and only annotations for safety, the description covers the critical unknowns: permissions, token absence, dry-run, and the TLS trap. It omits what is returned on success and whether region/pool names must be pre-listed, leaving a small gap.

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 82%, so the schema itself documents nearly all 11 parameters including tls and dryRun. The description reinforces the tls parameter's uniqueness to this tool but adds no formats or constraints beyond what the schema already states, so the baseline of 3 applies.

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 ("Create a new application (an image Gameye can run)") and clarifies its distinction from the sibling edit tool right in the same sentence. An agent can tell it apart from gameye_edit_application without opening either schema.

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 routing guidance: set TLS in this tool because gameye_edit_application drops it, and use dryRun=true to preview. It also states the required scope and the fallback when no token exists, so the agent knows the prerequisites and when this tool is the correct choice.

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