Skip to main content
Glama
MCP Dokploy Online
by igoruam

ai-suggest

Idempotent

Generates AI suggestions from provided input using a selected AI configuration, optionally scoped to a specific server.

Instructions

POST /ai.suggest

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>",
      "input": "<input>"
    },
    "name": "ai-suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
aiIdYes
inputYes
serverIdNo

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?

Annotations supply only openWorldHint=true and idempotentHint=true, so the description carries the full burden of behavioral disclosure and adds nothing. It does not state whether this consumes an AI provider/model, whether it requires credentials, whether it incurs cost or latency, or whether it mutates server-side state — all critical for an AI-inference endpoint. The POST method plus idempotentHint=true is ambiguous rather than contradictory, so this is a gap, not a contradiction.

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 short here reflects under-specification rather than economy — there is nothing to front-load because no real information is present. The endpoint string is not a useful summary for an agent choosing a tool.

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 three undocumented parameters, no output schema, and only two weak annotations, this definition leaves essentially every question an agent would need answered before calling it. The tool's complexity is not high, but the description provides no coverage at all.

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?

All three parameters (aiId, input, serverId) have 0% schema description coverage, so the description must compensate and does not. It gives no hint about what aiId references, what format 'input' expects (prompt text? JSON?), or when serverId is needed versus optional.

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 "POST /ai.suggest", which restates the tool name in HTTP-endpoint form. It conveys the transport method but nothing about what a 'suggest' operation actually does — no resource, no domain, no notion of what is being suggested or from what. An agent cannot distinguish this from siblings like ai-analyzeLogs or ai-create on the basis of this text.

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 conditions, no exclusions, and no reference to any alternative. The sibling list contains many ai-* tools, but the definition offers no signal about which one a given request should route to.

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