Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-get

Read-onlyIdempotent

Fetches a Dokploy AI configuration by its ID so you can inspect AI settings for deployment and infrastructure management.

Instructions

GET /ai.get

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": {
      "aiId": "<aiId>"
    },
    "name": "ai-get"
  }
}

Input Schema

NameRequiredDescriptionDefault
aiIdYes

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. The description contributes nothing beyond that — no statement of what is returned, whether a missing ID errors or returns null, or any access requirements.

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 that brevity reflects under-specification rather than economy: a bare route string with no front-loaded statement of purpose or scope. Nothing in the text earns its place because nothing informative is conveyed.

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?

For a one-parameter lookup with no output schema, the description should at minimum identify what entity is fetched and what aiId denotes. Neither is present, leaving the agent to guess at both input format and return shape.

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?

The single required parameter aiId has 0% schema description coverage, so the description carries the full burden of explaining it — and it says nothing. The agent cannot tell whether aiId is a name, numeric ID, UUID, or slug.

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?

"GET /ai.get" restates the tool name as an HTTP endpoint and adds no plain-language statement of what the tool actually does. It implies a read of a single 'ai' entity, but nothing distinguishes it from siblings such as ai-one or ai-getAll beyond the raw route.

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?

There is no when-to-use or when-not-to-use guidance at all, and no mention of alternatives like ai-getAll or ai-one. The agent must infer from the name alone that this fetches one AI resource.

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