Skip to main content
Glama

set_portainer_config

Configure Portainer connection settings including URL, API key, and endpoint ID to enable Docker container management through the VPS MCP Server.

Instructions

Configure Portainer connection settings (URL, API Key, Endpoint ID). The settings are saved to the .env file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPortainer URL (e.g., http://localhost:9000)
api_keyNoPortainer API Key (starts with ptr_)
endpoint_idNoDocker endpoint ID (usually 1 for local)
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds context by specifying that settings are saved to the .env file, which is useful beyond the basic 'configure' action. However, it lacks details on permissions, error handling, or side effects, leaving gaps for a mutation tool.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core action and resource, with a second clarifying sentence about the .env file. Every word earns its place, and there is no redundancy or unnecessary elaboration.

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?

Given the tool's moderate complexity (mutation with 3 parameters), no annotations, and no output schema, the description is minimally adequate. It covers the action and storage location but lacks details on outcomes, error cases, or dependencies, leaving the agent with incomplete context for safe invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema fully documents all three parameters. The description mentions the parameters by name but adds no additional semantic meaning beyond what's in the schema (e.g., no further constraints or usage notes), meeting the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Configure') and resource ('Portainer connection settings') with specific fields mentioned (URL, API Key, Endpoint ID), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_portainer_config' or 'test_portainer_connection', which prevents a score of 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_portainer_config' for retrieval or 'test_portainer_connection' for validation. It mentions the settings are saved to the .env file, but this is a behavioral detail rather than usage context, leaving the agent with no explicit when-to-use instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/onlitec/VPS-MCP-SERVER'

If you have feedback or need assistance with the MCP directory API, please join our Discord server