Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-getCustomProviders

Read-onlyIdempotent

Retrieves custom AI providers configured in Dokploy so you can review available provider integrations for AI-enabled deployments.

Instructions

GET /ai.getCustomProviders

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": "ai-getCustomProviders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered without the description. The description adds no behavioral context of its own — no note on what a "custom provider" contains, whether secrets are masked, or what the response shape is.

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 comes from under-specification rather than efficiency — the entire content is an endpoint path with no front-loaded statement of purpose. Nothing in the sentence tells an agent what it will get back.

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

Completeness2/5

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

With no output schema, the description is the only place that could describe return values, and it does not. For a zero-param read of a configuration-like resource, an agent is left guessing whether the result is a list, a map of provider IDs, or whether credentials are included.

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?

The tool takes zero parameters, and the schema is trivially complete, so there is no parameter semantics to add; the baseline for a no-param tool applies. No meaningful deduction is possible here, though the description also makes no use of the opportunity.

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 HTTP route "GET /ai.getCustomProviders", which restates the tool name rather than describing what the operation does. It implies retrieval of custom AI providers but never states the resource, scope, or return content in plain language.

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?

No when-to-use guidance is given, and no alternative is named despite siblings like ai-getEnabledProviders and ai-saveCustomProviders that clearly overlap in subject matter. The agent must infer the distinction from names 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