Skip to main content
Glama
Sign In

NEXUS AI

by io.github.nexusrun
OverviewDiscussions(2)Admin

Create Deployment

nexusai_deploy_create
Destructive

Create a deployment from a container image on NEXUS AI managed infrastructure or a connected AWS, Google Cloud or Azure account. Returns the deployment ID and status.

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": {
      "image": "<image>",
      "port": "<port>"
    },
    "name": "nexusai_deploy_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
portYes
imageYesContainer image (example: nginx:latest).
regionNo
envVarsNoNon-secret configuration only. Configure passwords, API keys, tokens, and credential-bearing URLs in the authenticated NEXUS AI dashboard, never in chat.
providerNodocker|gcp_cloud_run|aws_app_runner|azure_container_apps
requestIdNoOptional idempotency key.
environmentNoDeployment environment. Defaults to DEVELOPMENT.
startCommandNoOptional command to override the image default CMD (e.g. "node server.js").
autoDestroyHoursNo
healthCheckEnabledNoSet to false to disable health checks. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / description
      Previous value: -"docker|gcp_cloud_run|aws_ecs_fargate|azure_container_apps"New value: +"docker|gcp_cloud_run|aws_app_runner|azure_container_apps"
  2. Changed1 schema field changed
    • addedInput schema / properties / envVars / description
      Added value: +"Non-secret configuration only. Configure passwords, API keys, tokens, and credential-bearing URLs in the authenticated NEXUS AI dashboard, never in chat."
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=true, so the agent knows this is an externally visible, potentially destructive operation. The description adds that it returns the deployment ID and status, which is useful because there is no output schema, but it does not explain idempotency, auth requirements, secret-handling constraints, or why creation is marked destructive.

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?

The description is two sentences, front-loaded with the core action and platform scope, then immediately states the return value. There is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter deployment-creation tool with no output schema, the description is only minimally complete. It covers image-based creation, platform options, and return values, but omits operational context such as idempotency, environment defaults, auto-destroy behavior, health checks, and the critical secret-handling constraint that appears only in the schema.

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 description coverage is 64%, and the schema already documents key parameters including image, provider, envVars secret handling, requestId idempotency, environment defaults, startCommand, and healthCheckEnabled. The description only reiterates container image and provider platform choices, adding little meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create a deployment') and names the supported platforms, so the basic purpose is clear. It does not explicitly distinguish itself from nearby deploy siblings such as nexusai_deploy_redeploy or nexusai_deploy_source, but 'create from a container image' is reasonably discriminating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool instead of alternatives like redeploy, source-based deployment, or the provider-specific listing tools. The intended use is only implied by 'Create a deployment from a container image'; no prerequisites, exclusions, or sibling alternatives are stated.

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

All NEXUS AI toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources