action1-mcp-server

Initialize package file upload

action1_init_software_upload

Destructive

Starts a software package upload by creating an initial upload request for a specified package version and target platform.

Instructions

Not supported by this server (see error text). Initialize package file upload. Initializes package file upload. The client starts by sending the initial upload request. Perm: manage_software_repository.

Input Schema

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

Output Schema

Name	Required	Description	Default
`tool`	No
`value`	No
`dry_run`	No
`would_send`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

removedInput schema / properties / body / additionalProperties
```
Removed value: -{}
```

changedInput schema / properties / body / description

Previous value: -"Request body (schema: object)"New value: +"Request body"

removedInput schema / properties / body / type
```
Removed value: -"object"
```

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 / dry_run
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / value
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so safety context is partly covered. The description adds useful permission context ('Perm: manage_software_repository') and a protocol-sequence hint, but it does not explain what makes the operation destructive or how the unsupported-server note should affect invocation.

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

Conciseness2/5

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

The text is short but poorly structured: 'Initialize package file upload. Initializes package file upload.' is redundant, and leading with 'Not supported by this server (see error text)' is confusing rather than front-loading actionable information.

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?

The tool has annotations, a complete input schema, and an output schema, reducing what the description must cover. Still, it should clarify the relationship to action1_upload_software_chunk and explain whether 'Not supported by this server' means the tool should not be called at all.

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 explains the seven parameters, including required fields, confirm, dry_run, and platform enum. The description adds no parameter-level meaning beyond the permission note, so the baseline score of 3 applies.

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

Purpose3/5

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

It names a specific operation, 'Initialize package file upload,' and adds that the client starts by sending the initial upload request. However, the opening line 'Not supported by this server (see error text)' undermines the stated purpose, and the operation is repeated redundantly without distinguishing it from the related chunk-upload sibling.

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 implies this is the first request in an upload flow, but it gives no explicit guidance on when to use this tool versus alternatives such as action1_upload_software_chunk. The 'Not supported by this server' caveat creates ambiguity rather than routing guidance.

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

Deploy Server