EasyPanel MCP Server

Overview Schema Source Related Servers Discussions Admin

get_deployment

Retrieve detailed information about a specific deployment using its deployment ID. Get status, configuration, and other essential details for monitoring or troubleshooting.

Instructions

Get detailed information about a specific deployment.

Args: deployment_id: Deployment ID

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": {
      "deployment_id": "<deployment_id>"
    },
    "name": "get_deployment"
  }
}

Input Schema

Name	Required	Description	Default
`deployment_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. The verb 'Get' makes the read-only retrieval nature clear, but the description does not mention error behavior, preconditions, or side effects. Since an output schema exists, missing return-value details are less critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the core purpose. The 'Args' line is somewhat redundant with the schema, but it does not add meaningful bloat or confuse the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter getter, this is minimally viable, especially with an output schema provided. However, it lacks explicit differentiation from related tools and offers no context about when the deployment must exist or how failures are surfaced, leaving clear gaps.

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%, so the description needed to compensate for parameter meaning. It only restates the schema's own title—'Deployment ID'—adding no format, examples, or additional semantics. The impact is limited because there is only one obvious parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get detailed information about a specific deployment.' The word 'specific' clearly distinguishes it from sibling list_deployments, and 'information' separates it from logging tools like get_deployment_logs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: an agent would use this when it needs details about one known deployment. However, there is no explicit guidance about when to choose this over list_deployments or get_deployment_logs, and no alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.