Skip to main content
Glama
MCP Dokploy Online
by igoruam

sshKey-allForApps

Read-onlyIdempotent

Retrieves all SSH keys assigned to applications, helping you audit and manage app access credentials in Dokploy.

Instructions

GET /sshKey.allForApps

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sshKey-allForApps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description contributes nothing beyond that — no note on pagination, result size, auth requirements, or whether openWorld means the app list is fetched live from a remote source.

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 with no wasted words, but the brevity is under-specification rather than conciseness: a bare route string is not a front-loaded explanation of intent. One clarifying sentence about the "forApps" scope would have earned the space.

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?

With no output schema, the description is the only place to learn what comes back, and it says nothing about the return shape or the meaning of the app-scoped filter. For an open-world collection read, that leaves the agent guessing about both scope and response.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty closed object, so there is no parameter semantics to explain. Baseline 4 applies since nothing is left undocumented.

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 the raw HTTP route "GET /sshKey.allForApps", which restates the tool name rather than explaining it. It conveys that this reads a collection of SSH keys, but never defines what "allForApps" scopes to (keys attached to applications? app-scoped keys?) or how that differs from the sibling sshKey-all.

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 guidance, no prerequisites, and no mention of alternatives such as sshKey-all or sshKey-one, which are the obvious competing reads. An agent must infer selection purely from the tool name.

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