action1-mcp-server

Create a new report subscription

action1_create_report_subscription

Destructive

Creates a new report subscription to schedule recurring Action1 patch reports and set whether the subscription is enabled or disabled.

Instructions

Create a new report subscription. Creates a new report subscription. Perm: view_reports.

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
`self`	No
`tool`	No
`type`	No
`format`	No
`dry_run`	No
`comments`	No
`would_send`	No
`endpoint_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 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: +{
+  "name": {
+    "description": "URL of a user or API key assigned the role.\"",
+    "type": "string"
+  },
+  "report_id": {
+    "description": "ID of a report.",
+    "enum": [
+      "daily_patch_statistics",
+      "weekly_patch_statistics"
+    ],
+    "type": "string"
+  },
+  "schedule": {
+    "description": "Schedule settings string in the following format - **(ENABLED|DISABLED)...",
+    "type": "string"
+  }
+}

addedInput schema / properties / body / required

Added value: +[
+  "name",
+  "report_id",
+  "schedule"
+]

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 / comments
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / endpoint_count
```
Added value: +{}
```
addedOutput schema / properties / format
```
Added value: +{}
```
addedOutput schema / properties / id
```
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, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in the schema — the required permission 'view_reports' — but omits any warning about the destructive nature or the preview-then-confirm execution pattern.

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?

The first two sentences are a verbatim duplication of the same statement, which is pure waste in a three-sentence description. Only the trailing permission note carries new information.

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?

An output schema and rich annotations exist, so return values and safety signals are covered elsewhere. Still, for a destructive open-world mutation, the description should have explained the dry_run preview default and the confirm='YES' gate rather than leaving an agent to infer them from the schema.

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 all three parameters (body with name/report_id/schedule, confirm, dry_run) are documented in structured data. The description adds nothing about parameter meaning, so the baseline of 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 description states a clear verb and resource (create a report subscription), but it does so twice in nearly identical sentences, adding no specificity beyond the tool name and title. It does not distinguish this from sibling tools such as action1_update_report_subscription or action1_list_report_subscriptions.

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?

There is no guidance on when to use this versus update_report_subscription or list_report_subscriptions, and no mention of prerequisites or the confirm/dry_run workflow. Only the permission string 'Perm: view_reports' offers any contextual hint.

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

Deploy Server