kinsta_environments_ssh_configFetch SSH connection configuration for a Kinsta environment by supplying site ID and environment ID, giving you the details needed to connect.
Get SSH connection configuration for an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment ID | |
| site_id | Yes | The site ID |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and the description is consistent with a safe read operation. It adds no further behavioral context such as what the returned config contains, auth requirements, or rate limits, but there is no contradiction.
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 focused sentence with no redundant clauses, filler, or unnecessary detail. It is front-loaded and easy to parse.
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 read-only getter with fully documented parameters, this is minimally sufficient. However, with no output schema and many SSH-related siblings, it would benefit from stating what the SSH config includes or when to prefer this tool over ssh_status.
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 coverage is 100% with descriptions for both required IDs, so the baseline is 3. The description does not add parameter-level meaning beyond restating that the lookup is for an environment.
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 verb ('Get') and resource ('SSH connection configuration') scoped to an environment, matching the title. This is distinct from SSH siblings like ssh_status or ssh_toggle, which concern status or state changes rather than retrieving configuration.
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 the many SSH-related siblings such as ssh_status, ssh_toggle, ssh_password-access, or ip-allowlist. There are no exclusions or conditions, so an agent must infer usage from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.