action1-mcp-server

Close the entire enterprise associated with Action1 account

action1_request_enterprise_closure

Destructive

Close an entire Action1 enterprise account with a formal closure request. This tool terminates your associated enterprise profile safely and definitively.

Instructions

Close the entire enterprise associated with Action1 account. The request is available only for a free Action1 account. 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?

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds useful context beyond those annotations by stating the destructive scope is the entire enterprise and by naming the account-tier and permission prerequisites. It still does not explain reversibility or how this relates to revoking a closure.

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 three short sentences with the action and eligibility front-loaded, followed by the permission requirement. There is no wasted text.

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-wide operation, it covers scope, eligibility, and permission, and the schema covers confirm/dry_run and return structure via the output schema. The main missing context is the relationship to action1_revoke_enterprise_closure and any note about reversibility or downstream effects.

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 reason, confirm, and dry_run. The description adds no parameter-level detail beyond mentioning the required permission, so the baseline 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 action and resource: closing the entire enterprise associated with the Action1 account. It also adds an eligibility constraint. However, it does not explicitly distinguish this request from the closely related action1_revoke_enterprise_closure sibling or clarify whether closure is immediate versus requested.

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?

It clearly says the request is available only for a free Action1 account and requires manage_enterprise permission, which are important usage constraints. It does not explicitly say when to use this versus revoking a closure or updating the enterprise.

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

Deploy Server