Deletes a specified Terraform version from Blueprint integrations by version ID, removing obsolete versions from VCF Automation.
Deletes a terraform version DELETE /blueprint/api/blueprint-integrations/terraform/versions/{versionId}
| Name | Required | Description | Default |
|---|---|---|---|
| versionId | Yes | (path) | |
| apiVersion | No | The version of the API in yyyy-MM-dd format (UTC). For versioning information please refer to /blueprint/api/about |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond restating the operation and endpoint; it does not mention permanence, impact on dependent blueprints, or any side effects.
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 short and front-loaded with the action. The second line, an HTTP endpoint path, largely repeats the annotation title and is not especially informative, but the overall text is not verbose.
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 delete operation with complete parameter schema coverage and strong annotations, the description is minimally sufficient for invocation. However, it omits meaningful context such as whether deletion is irreversible, whether versions in use can be deleted, or any dependency on blueprints referencing the version.
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%, so both parameters are documented in the schema. The description adds no additional meaning about versionId or apiVersion beyond what the schema already provides, so the baseline score of 3 is appropriate.
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 and resource: 'Deletes a terraform version'. The HTTP DELETE path reinforces the operation. It does not explicitly differentiate itself from siblings like blueprint_get_terraform_version or blueprint_update_terraform_version, but the action and resource are clear.
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 guidance on when to use this tool versus alternatives such as updating, listing, or retrieving Terraform versions. No prerequisites or warnings are provided, aside from the implicit meaning of 'delete'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.