Skip to main content
Glama
MCP Dokploy Online
by igoruam

application-saveBuildType

Idempotent

Saves an application's build type and related settings in Dokploy, including Dockerfile, buildpack, or static-site options.

Instructions

POST /application.saveBuildType

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": {
      "applicationId": "<applicationId>",
      "buildType": "<buildType>",
      "dockerfile": "<dockerfile>",
      "dockerContextPath": "<dockerContextPath>",
      "dockerBuildStage": "<dockerBuildStage>",
      "herokuVersion": "<herokuVersion>",
      "railpackVersion": "<railpackVersion>"
    },
    "name": "application-saveBuildType"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildTypeYes
dockerfileYes
isStaticSpaNo
applicationIdYes
herokuVersionYes
railpackVersionYes
dockerBuildStageYes
publishDirectoryNo
dockerContextPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds nothing about behavior beyond them. It does not say whether existing build configuration is overwritten, what permissions or application state are required, or what happens to fields left null, which is critical for a mutation taking seven required parameters.

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

Conciseness2/5

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

It is brief, but the brevity is under-specification rather than conciseness: a single route path with no front-loaded statement of purpose. Nothing in it is structured to help an agent decide whether to call the tool.

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

Completeness1/5

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

For a 9-parameter mutation with 7 required fields, an enum-driven mode switch, and no output schema, the description provides no operational detail whatsoever. An agent could not correctly populate buildType-dependent parameters or predict the effect of the call from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, and the description mentions none of them. The enum values for buildType (dockerfile, nixpacks, railpack, static, etc.) and the coupled fields like dockerContextPath, dockerBuildStage, and publishDirectory receive no explanation of when each applies or how they interact.

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

Purpose2/5

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

The description is only the raw route string "POST /application.saveBuildType", which restates the tool name in HTTP form rather than describing what the operation accomplishes. It conveys that a build type is being persisted, but not what a build type is, what configuration it writes, or how it differs from siblings like application-saveDockerProvider.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no reference to any alternative tool. An agent has no stated condition to distinguish this from the provider-saving siblings or from build-triggering siblings such as application-killBuild.

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

Deploy Server

Other Tools