action1-mcp-server

Create an organization

action1_create_organization

Destructive

Create a new organization in Action1 by supplying a name and description, with required confirmation and optional dry-run preview before execution.

Instructions

Create an organization. Creates a new organization. Perm: manage_organizations.

Input Schema

Name	Required	Description
`body`	No	Request body
`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
`would_send`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

changedInput schema / properties / body / description

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

addedInput schema / properties / body / properties

Added value: +{
+  "description": {
+    "description": "Description for My Organization",
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  }
+}

addedInput schema / properties / body / required

Added value: +[
+  "name",
+  "description"
+]

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 / 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 / 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, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the mutation risk profile is known. The description adds one genuinely useful piece of context — the required permission scope — but says nothing about side effects, whether the caller becomes an org admin, or irreversibility beyond what annotations imply.

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?

Three short fragments, one of which is a pure duplicate of the opening sentence. The redundancy wastes the most salient position in the description and pushes the only useful detail (the permission) to the tail.

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?

With an output schema present and full schema coverage of the confirm/dry_run workflow, the description need not explain returns or parameters. It is minimally adequate, but for a destructive create-org operation it omits any note on scope of effect (e.g. does this create under the current enterprise) or what the required body fields mean.

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% and the schema itself documents the body fields plus the two-step safety mechanism (confirm="YES", dry_run defaulting to true). The description adds no parameter-level meaning, so baseline 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?

The verb+resource ("Create an organization") is unambiguous and implicitly distinguishes it from update_organization/delete_organization among siblings. However, the second sentence ("Creates a new organization") merely restates the first, adding zero information, and there is no explicit differentiation from siblings such as list_organizations or create_user.

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 only guidance is the permission requirement "Perm: manage_organizations." There is no statement of when to use this versus update_organization, what preconditions exist (e.g. name uniqueness), or any when-not-to-use guidance.

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

Deploy Server