AceDataCloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

acedatacloud_create_order

Create a single or batch recharge order for packages or applications by submitting their UUIDs, with confirmation required to finalize.

Instructions

Create a single or batch recharge order. The two modes are mutually exclusive.

Input Schema

TableJSON Schema

Name	Required	Description
`scope`	No	Optional order scope.
`confirm`	No	Must be true to create the order.
`metadata`	No	Optional order metadata.
`package_id`	No	Single package UUID.
`description`	No	Optional order description.
`package_ids`	No	Batch package UUIDs in matching order.
`application_id`	No	Single application UUID.
`application_ids`	No	Batch application UUIDs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.1.3Aug 21, 2026

addedInput schema / properties / application_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / application_id / default
```
Added value: +null
```

changedInput schema / properties / application_id / description

Previous value: -"UUID of the application to recharge. Required."New value: +"Single application UUID."

removedInput schema / properties / application_id / type
```
Removed value: -"string"
```

addedInput schema / properties / application_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Batch application UUIDs.",
+  "title": "Application Ids"
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true to actually create the order."New value: +"Must be true to create the order."

addedInput schema / properties / description

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional order description.",
+  "title": "Description"
+}

addedInput schema / properties / metadata

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional order metadata.",
+  "title": "Metadata"
+}

addedInput schema / properties / package_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / package_id / default
```
Added value: +null
```

changedInput schema / properties / package_id / description

Previous value: -"UUID of the package (quota bundle) to buy. Required."New value: +"Single package UUID."

removedInput schema / properties / package_id / type
```
Removed value: -"string"
```

addedInput schema / properties / package_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Batch package UUIDs in matching order.",
+  "title": "Package Ids"
+}

addedInput schema / properties / scope

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional order scope.",
+  "title": "Scope"
+}

removedInput schema / required

Removed value: -[
-  "application_id",
-  "package_id"
-]

Addedv0.1.1Jun 28, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only mentions mutual exclusivity of modes and does not disclose side effects, prerequisites, confirm semantics, reversibility, or financial impact of creating a recharge order. For a mutating financial tool, this is insufficient.

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 concise, containing two short sentences that convey the core purpose and a key constraint without wasted words. It is front-loaded and easy to parse.

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

Completeness2/5

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

Despite having an output schema, the description is under-specified for a create operation with 8 optional parameters, no required fields, and no annotations. It does not explain how to construct a valid single vs. batch request, the role of confirm, or the order lifecycle, leaving important invocation decisions unresolved.

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 each parameter is individually documented. The description adds the high-level statement that the two modes are mutually exclusive, which helps interpret single vs. batch parameter groups, but it does not provide additional detail beyond what parameter names and schema descriptions already convey.

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 states a specific action and resource: 'Create a single or batch recharge order.' It also distinguishes between two modes and is clear relative to siblings like list_orders, get_order, and pay_order, which serve different order lifecycle purposes.

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 such as create_auto_recharge, pay_order, or refresh_order. It does note that the two modes are mutually exclusive, but this only distinguishes single from batch, not when this tool should be selected over related order tools.

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

Deploy Server