Skip to main content
Glama
MCP Dokploy Online
by igoruam

destination-testConnection

Idempotent

Validates S3-compatible destination credentials and connectivity before saving. Use it to confirm bucket, region, endpoint, and access keys work for your storage provider.

Instructions

POST /destination.testConnection

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": {
      "name": "<name>",
      "provider": "<provider>",
      "accessKey": "<accessKey>",
      "bucket": "<bucket>",
      "region": "<region>",
      "endpoint": "<endpoint>",
      "secretAccessKey": "<secretAccessKey>"
    },
    "name": "destination-testConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
bucketYes
regionYes
endpointYes
providerYes
serverIdNo
accessKeyYes
additionalFlagsNo
secretAccessKeyYes

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 only declare openWorldHint=true and idempotentHint=true; the description adds nothing about what happens during the test (outbound call to the endpoint, credential validation, latency/rate considerations, failure modes). It neither contradicts the annotations nor expands on them, leaving the agent with no behavioral context beyond the structured hints.

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?

The text is short but that brevity reflects under-specification rather than economy; there is no front-loaded statement of purpose or structure. A single route token cannot earn its place as a tool description.

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?

For a 9-parameter credential-testing operation with no output schema and no parameter documentation, the description is completely inadequate. An agent has no basis to construct a valid invocation or interpret a result.

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?

Nine parameters with seven required and 0% schema description coverage, yet the description provides no meaning for any of them. Critical fields such as provider, endpoint, region, additionalFlags, and serverId are entirely undocumented, so an agent must guess their formats and constraints.

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 'POST /destination.testConnection', which restates the tool name rather than stating what the tool does. It never says that it validates storage destination credentials/connectivity (bucket, endpoint, region) or what a successful test means, so an agent cannot distinguish it from the many sibling *-testConnection tools.

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 prerequisites, and no mention of where this fits relative to destination-create, destination-update, or the other testConnection siblings. The route string supplies zero decision criteria.

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