Skip to main content
Glama

Edit application

gameye_edit_application
DestructiveIdempotent

Update an existing Gameye application with a partial PUT, changing only the fields you send; regions and ports replace whole lists. Preview changes with dryRun before applying.

Instructions

Admin tool. Change an existing application with PUT /application/{name}. Fields you omit stay unchanged; regions and ports, when given, replace the whole list. Warning: the server ignores tls on ports sent through edit and stores tls=false, so sending ports here turns off TLS on every port. Omit ports to keep existing TLS ports; set TLS ports with gameye_create_application. 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>"
    },
    "name": "gameye_edit_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the application to edit
portsNoContainer ports; replaces the whole list and stores tls=false on every port, whatever you send
dryRunNoReturn the exact request that would be sent, with the API token masked, and send nothing
limitsNo
regionsNoRegion names; replaces the whole list
tagKeepNoHow many image tags Gameye keeps for this application
nodePoolNoNode pool name
registryNoName 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
repositoryNoImage repository in that registry, without a tag
networkModeNoContainer network mode
reservationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A4.7/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: a non-obvious destructive side effect (the server ignores tls on edit and stores tls=false on every port), the required application:write scope, and the GAMEYE_API_TOKEN prerequisite with graceful fallback. The only gap is that it doesn't restate that omitted fields are preserved beyond a single clause on merge semantics — that is covered, so the disclosure is close to complete for a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose, then merge semantics, then the TLS warning, then auth and dryRun. Every sentence carries operational information; nothing is restated from the schema.

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?

For an 11-parameter destructive mutation with no output schema, the description covers what changes, what is preserved, what breaks, what permissions and credentials are needed, and how to safely preview. Nothing essential for correct invocation 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?

With 82% schema coverage the baseline is 3, and the description earns an upgrade by explaining merge-vs-replace semantics for regions and ports and the tls-stripping hazard that the schema only alludes to. It does not clarify limits, reservation, tagKeep, or nodePool, which remain schema-only.

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?

"Change an existing application with PUT /application/{name}" names a specific verb, resource, and HTTP endpoint, and explicitly contrasts itself with gameye_create_application for TLS port setup. An agent can distinguish this from create/list siblings without opening the 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 concrete decision rules: omit ports to preserve existing TLS ports, set TLS ports via gameye_create_application instead, and pass dryRun=true to preview. The alternative and the condition selecting it are both stated.

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