action1-mcp-server

Request a free trial or its extension

action1_request_enterprise_trial

Destructive

Secure a free enterprise trial or extend existing licenses. Manage enterprise access by submitting requests for trial periods or subscription extensions.

Instructions

Request a free trial or its extension. Perm: manage_enterprise.

Input Schema

Name	Required	Description
`body`	Yes	Request body (schema: SubscriptionPayload)
`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
`tool`	No
`type`	No
`status`	No
`dry_run`	No
`would_send`	No
`user_message`	No
`developer_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 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: +{
+  "comments": {
+    "description": "The additional comment.",
+    "type": "string"
+  },
+  "endpoint_count": {
+    "description": "The number of licensed endpoints for the enterprise.",
+    "type": "number"
+  }
+}

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 / developer_message
```
Added value: +{}
```
addedOutput schema / properties / dry_run
```
Added value: +{}
```
addedOutput schema / properties / id
```
Added value: +{}
```
addedOutput schema / properties / status
```
Added value: +{}
```
addedOutput schema / properties / tool
```
Added value: +{}
```
addedOutput schema / properties / type
```
Added value: +{}
```
addedOutput schema / properties / user_message
```
Added value: +{}
```
addedOutput schema / properties / would_send
```
Added value: +{}
```

First observedv0.5.0Jun 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the risk profile is carried by structured data. The description adds the auth requirement (manage_enterprise), which is genuine value, but it never explains the confirm/dry_run two-step safety ritual that a destructive-flagged tool would benefit from describing, nor what the trial request actually does to the enterprise.

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?

Two short sentences with the action front-loaded and the permission noted second; no wasted text. It is efficient, though the first sentence largely restates the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Wait — recalibrating: for a mutation tool, the description omits when an extension applies vs. a new trial and says nothing about the effects of execution. With annotations covering safety and an output schema present, the remaining gap is modest but real, so 3.

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 body, confirm and dry_run are already documented in the schema itself. The description adds nothing about parameter meaning, so the baseline 3 applies.

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 gives a specific verb and resource ('Request a free trial or its extension') and is clearly distinct from nearby siblings such as action1_request_enterprise_quote or action1_request_enterprise_closure. It does not explicitly name which sibling to prefer, 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?

The only usage information is the permission string 'Perm: manage_enterprise.' There is no guidance on when to use this versus requesting a quote, requesting closure, or getting the subscription, and no stated preconditions such as whether a trial must already exist to request an extension.

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

Deploy Server