Skip to main content
Glama

Get Edgegap container registry push credentials

edgegap_get_registry_credentials
Idempotent

Fetches push credentials for your organization's private Edgegap container registry plus exact docker login, build, and push commands when the server image isn't in a registry yet.

Instructions

Get the push login for this organization's private Edgegap container registry (registry.edgegap.com) and the exact docker login, build and push commands for your image. Use this when the server image is not in a registry yet. Edgegap only hands these credentials to the quick-start token the Unity/Unreal plugins use; with a regular API token this tool cannot fetch them and instead returns the steps to copy them from the dashboard's Container Registry page — ask the developer for them then, do not retry. When it does return a token, it is registry-scoped (push/pull images in this project), not the org API token: pass it to docker login via --password-stdin, never as a command-line argument, and do not write it into files. Call edgegap_validate_server_config before building. Any other registry Edgegap can pull from (Docker Hub, GHCR, ECR, GitLab) works too: then skip this tool and pass that registry and its pull login to edgegap_create_app_version.

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

Input Schema

NameRequiredDescriptionDefault
tagNoUnique build tag for the commands, e.g. a build ID. Never "latest".
image_nameNoImage name without project or tag, e.g. "my-game-server". Used to build the commands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false): discloses that credentials are only available with the quick-start token, that a regular API token returns steps instead and should not be retried, that the returned token is registry-scoped, and how to handle it securely (--password-stdin, not in files).

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 with purpose and immediate usage condition. Every sentence adds actionable context (auth caveat, token handling, validation step, alternative registries) without 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?

Given the tool's complexity (token scoping, conditional availability, security-sensitive handling) and absence of an output schema, the description covers all critical operational details an agent needs to call it correctly and handle the result.

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%, so the schema already documents 'tag' and 'image_name' fully. The description adds no parameter-specific syntax or meaning beyond what the schema provides; baseline 3 is appropriate.

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 (Get) and resource (push login for the private Edgegap container registry), including the registry domain. Distinguishes from siblings like edgegap_list_registry_tags and edgegap_create_app_version by focusing on credential retrieval for image push.

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?

Explicitly says when to use: 'Use this when the server image is not in a registry yet.' Also names alternatives and exclusions: if using Docker Hub, GHCR, ECR, or GitLab, skip this tool and pass the registry to edgegap_create_app_version. Guides to call edgegap_validate_server_config before building.

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