kinsta_environments_php-allocationAdjust PHP worker thread count and memory for a specific Kinsta environment, returning an operation ID to track the change.
Change PHP worker allocation for a specific environment. Returns an operation_id.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment ID | |
| thread_count | Yes | Number of PHP worker threads | |
| thread_memory | Yes | Memory per PHP worker thread in MB |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds one useful behavioral detail beyond the minimal openWorldHint annotation: it returns an operation_id, implying an asynchronous operation. However, it does not disclose side effects, whether changes take effect immediately, or how to track the operation's status.
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?
Two short, clear sentences with the core operation front-loaded and the return value stated separately. There is no filler or redundant information.
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 three-parameter mutation, the description covers the action and return value adequately. However, it does not point to the related operations_status tool for checking the returned operation_id, and it leaves potential confusion with the site-level allocation sibling unresolved.
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?
All three parameters are already documented in the input schema with 100% coverage. The description adds no additional constraints, defaults, or relationships between thread_count and thread_memory, so it provides no value beyond the schema.
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 clearly identifies the operation as changing PHP worker allocation for a specific environment, with the required resource and scope. However, it does not explicitly differentiate this tool from the closely named sibling kinsta_environments_php-allocation-site, so an agent may still face scope ambiguity.
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?
There is no explicit guidance on when to use this tool versus its site-level sibling, nor any mention of prerequisites or follow-up steps. The phrase 'for a specific environment' gives some context, but it does not help an agent decide between alternatives or understand the operational flow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.