kinsta_environments_ssh_toggleEnable or disable SSH/SFTP access for a Kinsta environment by providing its environment ID and a boolean flag. Control remote access to your site's infrastructure directly.
Enable or disable SSH/SFTP access for an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment ID | |
| is_enabled | Yes | Whether to enable (true) or disable (false) SSH |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The openWorldHint annotation signals a state-changing operation, and the description's 'Enable or disable' aligns with that. The description adds minimal extra behavioral context—no mention of impact on existing sessions, required permissions, or reversibility—but it does clarify the scope as environment-level SSH/SFTP access.
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 sentence with no filler. The action verb is front-loaded and every word contributes to the meaning, making it highly concise and well-structured.
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 simple two-parameter toggle with full schema coverage and no output schema, the description plus input schema is sufficient to invoke the tool correctly. It could optionally warn about side effects or point to related tools, but nothing essential is missing.
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?
Schema description coverage is 100%, with both env_id and is_enabled already documented clearly. The description adds no additional parameter-level meaning beyond what the schema provides, so it meets the baseline but does not exceed it.
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 uses specific verbs ('Enable or disable') and names the resource ('SSH/SFTP access') scoped to 'an environment', so an agent can identify it as an environment-level toggle. It doesn't explicitly distinguish itself from siblings like kinsta_sftp-users_toggle or kinsta_environments_ssh_status, so it misses the highest sibling-differentiation bar.
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?
The description gives no guidance on when to use this tool versus related siblings such as kinsta_environments_ssh_status or kinsta_sftp-users_toggle. There is no mention of prerequisites, context, or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.