Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-create

Create and configure an AI provider integration in Dokploy by supplying its name, API URL, API key, model, and enabled status.

Instructions

POST /ai.create

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>",
      "apiUrl": "<apiUrl>",
      "apiKey": "<apiKey>",
      "model": "<model>",
      "isEnabled": "<isEnabled>"
    },
    "name": "ai-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
modelYes
apiKeyYes
apiUrlYes
isEnabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

The only annotation is openWorldHint=true, so the description carries nearly the full burden of behavioral disclosure and delivers nothing. It does not say that credentials are persisted, whether creation is idempotent, what happens on duplicate names, or what the response contains.

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 short, but the brevity is under-specification rather than economy; a raw route string conveys no information an agent can act on. Nothing is front-loaded because there is effectively no content.

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 five-parameter, all-required mutation tool with no output schema and minimal annotations, the description should at least identify the created resource and note credential persistence. It supplies none of that, so the definition is not actionable on its own.

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?

Five required parameters exist with 0% schema description coverage, and the description adds no semantics for any of them. In particular apiUrl, apiKey, and isEnabled are undocumented in both places, leaving an agent to infer formats, secret handling, and default enablement behavior.

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 just "POST /ai.create", which restates the tool name in HTTP notation rather than explaining what an "AI create" produces. An agent cannot tell from this whether it registers a provider, creates a model configuration, or something else, and the required parameters apiUrl/apiKey/model hint at provider configuration only indirectly.

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

Usage Guidelines1/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 versus siblings like ai-saveCustomProviders, ai-update, or ai-testConnection. No preconditions, no ordering advice, no exclusion criteria are given, so an agent must guess from the name alone.

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