Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-getAll

Read-onlyIdempotent

Retrieves all AI-related resources from a Dokploy instance, letting you inspect available AI configurations and data in one call.

Instructions

GET /ai.getAll

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 help from the description. The description adds nothing beyond that — no indication of result volume, whether results are truncated or paginated, whether credentials/auth must be configured, or what happens when no AI providers exist.

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 brevity here reflects under-specification rather than economy — a single route string with no verb, no object, and no useful front-loaded information. There is nothing to trim, but also nothing that earns its place.

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 and no description of the return value, the agent has no idea what a successful response contains or how large it might be. For a zero-argument bulk-read tool the surface area is small, but a single clause explaining what is returned (and that it may be a large unfiltered collection) would be required to make this complete.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The empty object schema with additionalProperties=false is self-explanatory.

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.getAll", which restates the tool name (ai-getAll) in different notation rather than saying what it does. It implies a bulk retrieval of some AI-related resource, but never identifies what that resource is (providers, configurations, models) and gives no basis for distinguishing it from siblings like ai-get, ai-getModels, or ai-getEnabledProviders.

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 whatsoever about when to use this tool versus the many ai-* alternatives. An agent must infer from the name alone that this is the unfiltered list variant, which is exactly the kind of routing decision the description should make explicit.

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