action1-mcp-server

Revoke account closure

action1_revoke_enterprise_closure

Destructive

Revoke an Action1 enterprise closure to immediately reactivate the account and retain all data. Use this tool when a planned closure must be cancelled.

Instructions

Revoke account closure. The Action1 enterprise will be immediately reactivated and all your data will be retained. Perm: manage_enterprise.

Input Schema

Name	Required	Description
`body`	Yes	Request body (schema: EnterpriseRequest)
`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
`dry_run`	No
`verified`	No
`would_send`	No
`description`	No
`allowed_fast_closure`	No
`closure_requested_at`	No
`closure_requested_by`	No
`closure_scheduled_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 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: +{
+  "reason": {
+    "description": "Reason for closing.",
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / body / required
```
Added value: +[
+  "reason"
+]
```
- 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 / allowed_fast_closure
```
Added value: +{}
```
- addedOutput schema / properties / closure_requested_at
```
Added value: +{}
```
- addedOutput schema / properties / closure_requested_by
```
Added value: +{}
```
- addedOutput schema / properties / closure_scheduled_at
```
Added value: +{}
```
- addedOutput schema / properties / description
```
Added value: +{}
```
- addedOutput schema / properties / dry_run
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / name
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / tool
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
- addedOutput schema / properties / verified
```
Added value: +{}
```
- addedOutput schema / properties / would_send
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations, the description discloses the key outcome: the enterprise is immediately reactivated and data is retained. It also names the required permission. It does not explain confirm/dry_run behavior, but that is documented in the schema and output schema, and the annotations already cover the destructive/open-world nature.

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?

Three short sentences, front-loaded with the action and outcome. The permission note is compact and nothing is wasted.

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

Completeness4/5

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

For a destructive enterprise-level mutation, the description covers the action, immediate effect, data retention, and required permission. With annotations and a rich schema carrying confirmation and dry-run semantics, this is nearly complete, though a sentence about when the enterprise is eligible for revocation would close the remaining gap.

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 body.reason, confirm, and dry_run. The description adds only the manage_enterprise permission requirement and does not add syntax or semantic detail beyond the schema.

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 verb and resource: revoke an account closure. It is clearly the inverse of the sibling action1_request_enterprise_closure, and an agent can distinguish it from update_enterprise or get_enterprise without opening the schema.

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

Usage Guidelines3/5

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

The description implies the tool is used to reverse a previously requested enterprise closure and notes the required manage_enterprise permission. It does not explicitly state when to use it versus action1_request_enterprise_closure or action1_update_enterprise, nor does it list exclusions or preconditions beyond the permission.

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

Deploy Server