kinsta_environments_ssh_password-accessEnable or disable SSH password authentication for a Kinsta environment using the environment ID. Manage secure access by toggling password-based login on or off.
Enable or disable SSH password-based access for an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment ID | |
| is_enabled | Yes | Whether to enable (true) or disable (false) password access |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description communicates that this is a mutating toggle but does not disclose side effects, such as whether existing SSH passwords remain valid, whether access is immediately revoked, or whether authentication state is affected. The annotations only include openWorldHint, which does not cover behavioral safety or mutation details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that directly states the tool's purpose. It is appropriately concise for a simple two-parameter toggle operation with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity toggling tool with fully documented parameters, the description is minimally viable. However, it lacks usage guidance and behavioral context, which leaves some ambiguity about how this differs from the many SSH-related sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully describes both parameters (env_id and is_enabled) with 100% coverage. The description adds little beyond restating that is_enabled controls enabling/disabling, which aligns with the schema's boolean description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Enable or disable') on a clear resource ('SSH password-based access for an environment'). It is clear and distinct from the generic sibling kinsta_environments_ssh_toggle, though it does not explicitly name that alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus related SSH tools such as kinsta_environments_ssh_toggle, kinsta_environments_ssh_password, or kinsta_environments_ssh_status. The usage context must be inferred entirely from the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.