action1-mcp-server

Update enterprise settings

action1_update_enterprise

Destructive

Update the current enterprise's name and description settings, with a preview-first dry run and explicit confirmation before execution.

Instructions

Update enterprise settings. Updates settings for a current enterprise. Perm: manage_enterprise.

Input Schema

Name	Required	Description
`body`	No	Request body (schema: EnterprisePayload)
`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.

Changed17 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": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  }
+}
```
- 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

C2.9/5.0

Behavior3/5

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

Adds real value beyond annotations with the permission requirement ("Perm: manage_enterprise"), which annotations do not convey. However, for a tool flagged destructiveHint=true and idempotentHint=false, it says nothing about the preview-then-execute pattern, partial-update semantics, or that omitted fields are left unchanged.

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

Conciseness3/5

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

Very short and front-loaded, which is good, but the second sentence is pure restatement and the permission note is appended without structure. Space that could have held the confirm/dry_run contract is spent on redundancy.

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?

An output schema exists, so return values need not be explained, but this is a destructive, non-idempotent mutation with a nested payload and a required-confirmation gate, and the description covers none of that. For its complexity the definition leaves too much for the schema to carry.

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, confirm, and dry_run — baseline 3. The description adds no field-level meaning such as whether name/description are optional or how an empty body is handled.

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?

States a specific verb and resource ("Update enterprise settings") that clearly maps to the enterprise-level object, distinguishable from siblings like action1_get_enterprise or action1_update_organization. The second sentence restates the same idea rather than narrowing scope further.

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?

No guidance on when to use this versus siblings, no preconditions, and nothing about the two-step dry_run/confirm workflow implied by the schema. An agent must open the schema and infer the safe invocation sequence itself.

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

Deploy Server