Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-analyzeLogs

Idempotent

Analyzes build or runtime logs with AI to identify errors, root causes, and actionable fixes for Dokploy deployments.

Instructions

POST /ai.analyzeLogs

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>",
      "logs": "<logs>",
      "context": "<context>"
    },
    "name": "ai-analyzeLogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
aiIdYes
logsYes
contextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

The description adds nothing beyond the annotations, which only declare openWorldHint and idempotentHint. It doesn't say what the AI does with the logs, whether it incurs cost or latency, whether results are deterministic, or what failures look like — and with no readOnly/destructive hints, those unknowns matter.

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 brief, but this is under-specification rather than conciseness — a bare route string that earns none of its place as guidance. There is no structure or front-loaded explanation to speak of.

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?

A tool with three required undocumented parameters, no output schema, and no annotations covering safety or semantics needs a description to carry the load. This one says nothing, leaving the agent unable to invoke it correctly beyond guessing from parameter names.

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?

Schema description coverage is 0% across three required parameters (aiId, logs, context), and the description provides no compensating meaning. It never explains what aiId refers to, what format the logs string should take, or how 'build' vs 'runtime' context changes behavior.

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 an HTTP route string, 'POST /ai.analyzeLogs', which restates the name in URL form. It implies an AI-driven log analysis action but never states what analyzing logs means or what the tool returns, and it does nothing to distinguish itself from siblings like application-readLogs or deployment-readLogs that also deal with logs.

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 exclusions, and no mention of alternatives such as the readLogs tools. An agent has no way to know from the description when this analysis tool is the right choice over simply reading logs.

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