action1-mcp-server

Clone Software Repository package

action1_clone_package

Destructive

Clone an existing Software Repository package into a new package ID, using a dry-run preview to confirm the copy before execution.

Instructions

Clone Software Repository package. Creates a full copy of an existing Software Repository package under a new package ID. Perm: manage_software_repository.

Input Schema

Name	Required	Description
`org_id`	No	Org UUID.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.
`package_id`	Yes	Provide a specific package ID.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`self`	No
`tool`	No
`type`	No
`scope`	No
`status`	No
`vendor`	No
`builtin`	No
`dry_run`	No
`versions`	No
`would_send`	No
`description`	No
`internal_notes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.6.0Oct 26, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / builtin
```
Added value: +{}
```
- addedOutput schema / properties / description
```
Added value: +{}
```
- addedOutput schema / properties / dry_run
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / internal_notes
```
Added value: +{}
```
- addedOutput schema / properties / name
```
Added value: +{}
```
- addedOutput schema / properties / scope
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / tool
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
- addedOutput schema / properties / vendor
```
Added value: +{}
```
- addedOutput schema / properties / versions
```
Added value: +{}
```
- addedOutput schema / properties / would_send
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description confirms the operation is a creation/write action and that a copy is made. Since the annotations already flag it as 'destructiveHint: true', the description mainly reiterates the action's result, adding moderate clarity without revealing hidden operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, using exactly what is needed: first, defining the core function, and second, defining the authorization context. There is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the comprehensive nature of the schema and annotations, the description provides all necessary functional and authorization context for an agent to correctly identify and use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the schema already provides full semantic meaning for all parameters. The description's focus remains on the high-level function rather than parameter details, maintaining the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is highly specific, clearly defining the action (Clone), the resource (Software Repository package), and the outcome (Creates a full copy under a new package ID). This makes it very easy for an agent to select this tool over related create or retrieval actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

By specifying the required permission ('Perm: manage_software_repository.'), the description provides critical usage guidance regarding the tool's authorized scope. This is necessary context for an agent to decide if it is permitted to invoke the tool in a given environment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server