Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-all

Read-onlyIdempotent

List all projects from a connected Dokploy instance to review deployments and select the project needed for infrastructure management tasks.

Instructions

GET /project.all

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": "project-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 without the description. The description adds nothing beyond that — no pagination, ordering, scope, or auth context — and notably gives no hint about what the open-world behavior actually entails.

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 concision. A raw route string is not a front-loaded statement of purpose.

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?

The tool is simple (no params, read-only), but with no output schema and no description of return contents, volume, or pagination behavior, an agent knows only that a GET exists on that path. That is inadequate for reliably choosing and calling it among many project-* siblings.

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 schema has zero parameters (100% coverage), so there is nothing for the description to disambiguate. Per the zero-parameter baseline, the absence of parameter discussion is not a defect.

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?

"GET /project.all" only restates the tool name as a raw HTTP endpoint. It implies a list-everything read of projects, but offers no verb-level statement of what is retrieved or how it differs from siblings such as project-allForPermissions or project-search.

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. An agent cannot tell from this text whether to call project-all, project-allForPermissions, or project-search for a given need.

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