Skip to main content
Glama
MCP Dokploy Online
by igoruam

project-one

Read-onlyIdempotent

Retrieve details for a specific Dokploy project by its project ID, enabling inspection of project configuration and status.

Instructions

GET /project.one

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": {
      "projectId": "<projectId>"
    },
    "name": "project-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 fully covered. The description adds nothing beyond the verb "GET": no return shape, no 404/not-found behavior, no permission requirements. It does not contradict the annotations, but it contributes essentially no behavioral context.

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 this is under-specification rather than conciseness: a raw endpoint path rather than a front-loaded statement of purpose. There is no structure to speak of, and every word present is just a route reference.

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 itself is simple (one required param, no output schema), and annotations cover the read-only/idempotent profile, so the bar is modest. Still, an agent gets no confirmation of what is returned or what identifies a project, leaving the definition short of the minimum needed to invoke confidently.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter projectId, and the description supplies no compensating meaning — it does not clarify whether the value is a UUID, numeric ID, or slug. The parameter name is largely self-explanatory, which keeps this above the floor, but nothing is added beyond the schema.

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.one" only restates the tool name plus the HTTP verb, which merely echoes the readOnlyHint annotation. It never says in plain language that it retrieves a single project record, nor does it distinguish itself from siblings such as project-all or project-search beyond the ambiguous ".one" suffix.

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 at all — no statement that this is for fetching one project by ID versus listing (project-all) or searching (project-search). No prerequisites, no conditions, no exclusions.

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