Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-saveCustomProviders

Idempotent

Saves custom AI provider configurations, including names and API URLs, to your Dokploy instance for use in AI integrations.

Instructions

POST /ai.saveCustomProviders

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": {
      "providers": "<providers>"
    },
    "name": "ai-saveCustomProviders"
  }
}

Input Schema

NameRequiredDescriptionDefault
providersYes

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?

Annotations only declare openWorldHint=true and idempotentHint=true, leaving destructiveHint and readOnlyHint unstated, so the description carries the full burden of disclosing that this is a mutating save. It discloses nothing: no statement on whether the list replaces or merges with existing providers (additionalProperties=false and a full required array suggest replacement, but the description never confirms it), no auth requirements, no failure behavior.

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?

The text is short, but it is under-specified rather than concise: a route string is not front-loaded intent. There is no structure to speak of, just an endpoint label.

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 mutation tool with a nested required payload, no output schema, and sparse annotations, the definition provides none of the context an agent needs to call it safely or correctly. The replacement-vs-append semantics of the providers array, the most consequential unknown, is left entirely unaddressed.

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% for the single required `providers` array, and the description says nothing about its nested name/apiUrl fields, format expectations, or whether the array is a complete replacement set. The schema names the fields but no semantic meaning is added anywhere.

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?

"POST /ai.saveCustomProviders" only restates the tool name as an HTTP route. It never explains what saving custom providers does, what a provider represents, or how the result differs from the sibling ai-getCustomProviders. An agent reading only this line learns nothing beyond the name.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternative ai-getCustomProviders or ai-getEnabledProviders for reading existing configuration. The agent must guess that this is the write counterpart to those reads.

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