action1-mcp-server

Request a quote

action1_request_enterprise_quote

Destructive

Submit an enterprise quote request to Action1 Sales with product, endpoint count, and comments; preview the request before confirming execution.

Instructions

Request a quote. Sends a quote request to the Action1 Sales department. Perm: manage_enterprise.

Input Schema

Name	Required	Description
`body`	Yes	Request body (schema: SubscriptionQuotePayload)
`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"
+  },
+  "product": {
+    "description": "Company 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 / 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 openWorldHint=true and destructiveHint=true, so the agent knows this makes an external, non-reversible side effect. The description adds the required permission (manage_enterprise), which is genuinely useful, but says nothing about the confirm/dry_run safety flow that is central to invoking this tool safely.

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 purpose and followed by the destination and permission requirement. No filler, though the title simply repeats the first sentence.

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 exists and the schema fully documents parameters, so the bar is lower. Still, for an outward-facing request to a human sales team, the description omits what happens next (ticket creation, response expectations) and does not flag the dry_run-default-true behavior an agent must override.

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 nested body fields, the required "YES" confirm constant and the dry_run default are all already documented in the schema. The description adds no parameter meaning beyond that, so 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?

States a specific verb and resource ("Request a quote") and adds the audience ("Sends a quote request to the Action1 Sales department"). That distinguishes it from trial/closure siblings in substance, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance; an agent must infer that this is the sales-contact path rather than action1_request_enterprise_trial or action1_request_enterprise_closure. The "Perm: manage_enterprise" prerequisite is the only concrete usage signal.

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

Deploy Server