Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-one

Read-onlyIdempotent

Retrieve a specific AI record from a Dokploy instance by its AI ID to inspect settings for management or deployment tasks.

Instructions

GET /ai.one

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

Input Schema

NameRequiredDescriptionDefault
aiIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/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 elsewhere. The description adds nothing beyond that — no note on what is returned, whether a missing id errors, or remote-provider implications of openWorldHint.

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 technically short with no wasted words, but this is under-specification rather than conciseness. A single raw HTTP route is not an adequate front-load of information.

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?

With no output schema, no parameter documentation and no annotations explaining return shape, the description must carry the burden and does not. An agent cannot tell what this call yields or how the id is formed.

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

Parameters1/5

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

The single parameter aiId has 0% schema description coverage, so the description is the only place the identifier's meaning could be explained, and it says nothing. Whether aiId is a slug, UUID, or provider-scoped key is left entirely ambiguous.

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 just the HTTP route "GET /ai.one", which restates the tool name rather than stating a verb and resource in natural language. An agent can infer it retrieves a single AI by id, but nothing in the text confirms the resource meaning or distinguishes it 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 mention of alternatives such as ai-get or ai-getAll, and no prerequisites or exclusions. The agent must guess entirely from the endpoint string.

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