Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-getEnabledProviders

Read-onlyIdempotent

Fetches the list of enabled AI providers from your Dokploy instance so you can verify which providers are available for client connections.

Instructions

GET /ai.getEnabledProviders

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-getEnabledProviders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the read-only, idempotent safety profile is fully covered by structured data. The description adds no behavioral context whatsoever – no mention of whether results depend on configuration state, whether the list can be empty, or what external systems are consulted despite openWorldHint=true.

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 single line is free of filler but is under-specified rather than concise – it conveys no information beyond a routable identifier. There is no front-loaded statement of purpose or scope to anchor the agent.

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 carries the burden of explaining what is returned, and it does not: it never says whether the response is a list of provider names, configuration objects, or model catalogs. For a zero-parameter listing tool this gap is small but material, since an agent cannot tell the shape or scope of the result, nor how this list differs from the custom-provider listing.

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

Parameters4/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 empty with additionalProperties=false, so there is nothing for the description to clarify. Baseline 4 applies for a parameterless tool; no parameter meaning is missing.

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.getEnabledProviders', which paraphrases the tool name rather than explaining what it does. An agent can infer that it reads enabled AI providers, but nothing states what an 'enabled provider' is or what the result contains, and it does not distinguish it from siblings like ai-getCustomProviders, ai-getModels, or ai-getAll.

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?

No when-to-use guidance, no conditions for choosing this over ai-getCustomProviders or ai-getAll, and no prerequisites. The GET verb implies a read-only listing but that is already conveyed by the name and annotations.

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