Skip to main content
Glama
MCP Dokploy Online
by igoruam

environment-one

Read-onlyIdempotent

Retrieves details for a specific Dokploy environment using its environment ID, helping you inspect configuration and status for deployment and infrastructure management.

Instructions

GET /environment.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": {
      "environmentId": "<environmentId>"
    },
    "name": "environment-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
environmentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered externally. The description adds nothing beyond that: no note on what is returned, whether a missing id errors or returns empty, or that the operation reaches an external service. It contributes zero behavioral context on top of 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?

It is short with no wasted words, but that brevity is under-specification rather than conciseness. A raw HTTP route is not a useful front-loaded summary of intent for an AI agent.

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 tool that fetches an external environment resource with one undocumented required parameter and no output schema, the description should at minimum state what is fetched and what happens on failure. None of that is present.

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?

There is a single required parameter, environmentId, with 0% schema description coverage, so the description is the only place its meaning could be explained. Instead it supplies nothing about format, source of the id, or behavior when the id is unknown; the only signal is the parameter's self-evident name.

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 route string "GET /environment.one", which essentially restates the tool name plus an HTTP verb. It does imply retrieving a single environment object (singular, one), but gives no resource scope, no description of what an 'environment' contains, and no differentiation from siblings such as environment-byProjectId or environment-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 guidance at all about when to use this tool, when to prefer the search or byProjectId siblings, or what preconditions must hold (e.g., a valid, existing environment id). An agent must infer usage purely from the 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