kinsta_environments_ssh_ip-allowlistRetrieve the SSH IP allowlist for a Kinsta environment using its environment ID to see which IPs can connect via SSH.
Get the SSH IP allowlist for an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment 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, so the description's 'Get' adds no behavioral information beyond those hints. No response format, authentication nuance, or other runtime behavior is disclosed. No contradiction exists.
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?
One clear sentence with no filler. The action and resource are front-loaded, and the length is appropriate for a single-parameter read-only tool.
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 one-parameter, read-only tool with strong annotations, the description plus schema provide enough to invoke it correctly. The lack of an output schema means the exact return shape is unstated, but the resource name is self-explanatory; a small note on what the allowlist contains would make it fully complete.
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% and the only parameter env_id is described as 'The environment ID' in the schema. The description adds no additional meaning about the ID format, source, or relationship to other Kinsta resources, so the baseline of 3 applies.
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 a specific verb ('Get') and a specific resource ('SSH IP allowlist') scoped to an environment. It clearly positions this tool as the read operation alongside the sibling 'kinsta_environments_ssh_ip-allowlist_update', so an agent can distinguish them without opening schemas.
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 given on when to use this tool versus alternatives. The description does not mention that changes are handled by the update sibling or distinguish it from other SSH-related tools; the read intent is only implied by the word 'Get'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.