action1-mcp-server

Create a data source

action1_create_data_source

Destructive

Define a new custom enterprise data source by supplying a name, description, and PowerShell script. Specify output columns to structure the data and make it available for use.

Instructions

Create a data source. Creates a new custom data source. At this time, all data sources are enterprise-wide. Perm: manage_data_sources.

Input Schema

Name	Required	Description
`body`	Yes	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
`status`	No
`builtin`	No
`columns`	No
`dry_run`	No
`language`	No
`would_send`	No
`description`	No
`script_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 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: +{
+  "columns": {
+    "description": "A list of data source output columns.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "description": {
+    "description": "The data source description.",
+    "type": "string"
+  },
+  "language": {
+    "description": "The language for querying data.",
+    "enum": [
+      "PowerShell"
+    ],
+    "type": "string"
+  },
+  "name": {
+    "description": "The name of the data source.",
+    "type": "string"
+  },
+  "script_text": {
+    "description": "The script text.",
+    "type": "string"
+  },
+  "status": {
+    "description": "This parameter is currently deferred.",
+    "enum": [
+      "Published",
+      "Draft"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / body / required

Added value: +[
+  "name",
+  "description",
+  "language",
+  "script_text",
+  "columns",
+  "status"
+]

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 / builtin
```
Added value: +{}
```
addedOutput schema / properties / columns
```
Added value: +{}
```
addedOutput schema / properties / description
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / id
```
Added value: +{}
```
addedOutput schema / properties / language
```
Added value: +{}
```
addedOutput schema / properties / name
```
Added value: +{}
```
addedOutput schema / properties / script_text
```
Added value: +{}
```
addedOutput schema / properties / self
```
Added value: +{}
```
addedOutput schema / properties / status
```
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

B3.1/5.0

Behavior3/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context — data sources are enterprise-wide and the caller needs the manage_data_sources permission — but omits the two-step dry_run/confirm='YES' behavior, which is the most consequential operational detail.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action, and the permission note is a useful trailing cue. The opening two sentences are redundant with each other, a small waste of space.

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?

For a destructive, non-idempotent creation tool with a required confirm='YES' parameter and a dry_run default of true, a description that never explains execution vs preview leaves the agent at real risk of a failed or unintended call. Output schema richness offsets this only partly.

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 coverage is 100%, so the baseline is 3; the nested body fields and the confirm/dry_run parameters are all documented in the schema. The description adds no parameter-level meaning of its own and never mentions confirm or dry_run.

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+resource ('Create a data source' / 'Creates a new custom data source') that clearly separates it from the list/get/update/delete_data_source siblings. The second sentence is largely a restatement of the first, so it stops short of a 5.

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 create a data source versus reusing an existing one, and no mention of the preview/confirm workflow that governs actually executing this call. The agent must infer everything from the schema.

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

Deploy Server