action1-mcp-server

Create new Software Repository package

action1_create_package

Destructive

Create a new Software Repository package with no versions and set its initial basic details including name, vendor, platform, and description.

Instructions

Create new Software Repository package. Create a new custom Software Repository package object (with no versions) and set its initial basic. Perm: manage_software_repository.

Input Schema

Name	Required	Description
`body`	Yes	Request body (schema: SoftwareRepositoryPackagePayloadPost)
`org_id`	No	Org UUID.
`confirm`	No	Required to execute. Exact string "YES".
`dry_run`	No	Default true (preview). Set false to execute.

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.

Changed19 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"

addedInput schema / properties / body / properties

Added value: +{
+  "description": {
+    "description": "The package description.",
+    "type": "string"
+  },
+  "internal_notes": {
+    "description": "Invisible comments.",
+    "type": "string"
+  },
+  "name": {
+    "description": "The package name.",
+    "type": "string"
+  },
+  "platform": {
+    "description": "The package platform.",
+    "enum": [
+      "Windows",
+      "Mac"
+    ],
+    "type": "string"
+  },
+  "vendor": {
+    "description": "The package vendor.",
+    "type": "string"
+  }
+}

addedInput schema / properties / body / required

Added value: +[
+  "name",
+  "vendor",
+  "description",
+  "platform"
+]

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

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds useful context—the required permission ('manage_software_repository') and the fact that no versions are created—but does not explain the confirm/dry_run workflow or what 'set its initial basic' means.

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

Conciseness4/5

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

The description is front-loaded with the action and resource, and it is reasonably concise. The phrase 'set its initial basic' is awkward and slightly unclear, keeping it from a perfect score, but there is no wasted text.

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

Completeness3/5

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

Given the output schema and 100% schema description coverage, the description covers the core purpose and permission requirement. However, it omits explanation of the confirm/dry_run execution safety mechanism and leaves 'initial basic' undefined, so it is only minimally complete for a creation tool with nested payload.

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?

Schema description coverage is 100%, so the schema already documents all parameters including the nested body fields. The description contributes no additional parameter details beyond the vague phrase 'set its initial basic', 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.

Purpose4/5

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

The description states a specific verb ('Create') and resource ('Software Repository package object'), and clarifies it creates the package 'with no versions', which distinguishes it from action1_create_package_version. It does not explicitly name alternatives, but the scope detail is sufficient to separate it from most siblings.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like action1_clone_package or action1_create_package_version. The only additional context is the required permission, which is not a usage guideline.

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

Deploy Server