Action1 MCP Server

by ComTom777

Overview Schema Source Related Servers Discussions Admin

Python

Remote

run_script

Destructive

Execute a PowerShell script as SYSTEM on specified endpoints, then return each endpoint's status and stdout output.

Instructions

Run a PowerShell script now, as SYSTEM, on the given endpoints (ids from list_endpoints) and wait up to wait_seconds for results. Returns each endpoint's status and output (stdout, capped at ~10,000 chars by Action1). Never reboots. Offline endpoints stay pending - check later with list_automation_instance_endpoint_results(instance_id).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "org_id": "<org_id>",
      "endpoint_ids": "<endpoint_ids>",
      "script": "<script>"
    },
    "name": "run_script"
  }
}

Input Schema

Name	Required	Description	Default
`org_id`	Yes
`script`	Yes
`endpoint_ids`	Yes
`wait_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the destructiveHint=true/readOnlyHint=false annotations: it discloses SYSTEM privilege, synchronous wait semantics, stdout truncation at ~10,000 chars, 'never reboots', and that offline endpoints remain pending. These are exactly the operational traits an agent needs before firing a remote script.

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

Conciseness5/5

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

Four tight sentences, front-loaded with the action and privilege context, with no filler. Each clause (return format, no reboot, offline handling) carries distinct operational value.

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?

For a destructive synchronous mutation with no output schema, the description covers privilege level, return shape (status + capped stdout), reboot behavior, and the async/offline path. Nothing an agent needs to call it safely and correctly is missing.

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 0%, so the description must carry the load. It clarifies wait_seconds ('wait up to wait_seconds') and endpoint_ids provenance (ids from list_endpoints) and implies script is PowerShell, but org_id is entirely unexplained and no formats/defaults are given, so the low-coverage schema is only partially compensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Run), resource (PowerShell script), execution target (given endpoints) and privilege context (as SYSTEM, now = synchronous). This clearly separates it from siblings like deploy_updates (patch deployment) and the list_* read tools.

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

Usage Guidelines4/5

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

Gives concrete routing: endpoint ids come from list_endpoints, and offline endpoints 'stay pending - check later with list_automation_instance_endpoint_results(instance_id)'. This is real alternative/context guidance, though it never explicitly states when to prefer this over a scheduled automation or deploy_updates.

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