Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-getModels

Read-onlyIdempotent

Fetches available AI models from a Dokploy instance using an API URL and key, helping you select valid model options for AI-powered deployment and automation tasks.

Instructions

GET /ai.getModels

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": {
      "apiUrl": "<apiUrl>",
      "apiKey": "<apiKey>"
    },
    "name": "ai-getModels"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYes
apiUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 safety and idempotency are covered structurally. The description contributes nothing beyond that - no mention of authentication requirements beyond the apiKey param, no rate limits, no indication of what the model list 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?

The text is minimal, but this is under-specification rather than conciseness; it conveys no information an agent could act on. There is no structure to front-load.

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 tool with two required, undocumented parameters, no output schema, and no annotation commentary in text, the definition says nothing about return values, error behavior, or authentication setup. It is inadequate for invoking the tool correctly without guessing.

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

Parameters2/5

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

Schema description coverage is 0% for apiUrl and apiKey, so the description needs to compensate and does not. The names are largely self-explanatory, but nothing is said about expected URL format, key scope, or whether the key must have particular permissions.

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 endpoint string "GET /ai.getModels", which restates the tool name (ai-getModels) rather than describing what it does. An agent learns the HTTP verb at best; it cannot tell from this text how listing models differs from siblings like ai-get 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 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 alternatives such as ai-get, ai-getEnabledProviders, or ai-getCustomProviders. The agent must infer selection 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