action1-mcp-server

Get a specific script

action1_get_script

Read-onlyIdempotent

Retrieve details for a specific Action1 script by ID to inspect its configuration and support script management tasks.

Instructions

Get a specific script. Gets details for a script specified by its ID. Perm: use_scripts.

Input Schema

Name	Required	Description
`verbose`	No	Skip per-item compactor.
`script_id`	Yes	Provide a specific script ID.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`self`	No
`type`	No
`params`	No
`status`	No
`builtin`	No
`language`	No
`description`	No
`script_text`	No
`enterprise_id`	No
`success_codes`	No
`reboot_exit_codes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 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"
```
- 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 / description
```
Added value: +{}
```
- addedOutput schema / properties / enterprise_id
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / language
```
Added value: +{}
```
- addedOutput schema / properties / name
```
Added value: +{}
```
- addedOutput schema / properties / params
```
Added value: +{}
```
- addedOutput schema / properties / reboot_exit_codes
```
Added value: +{}
```
- addedOutput schema / properties / script_text
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / status
```
Added value: +{}
```
- addedOutput schema / properties / success_codes
```
Added value: +{}
```
- addedOutput schema / properties / type
```
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 declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a real piece of context with 'Perm: use_scripts', but says nothing about what 'verbose' does to output or how response_format affects the result beyond what the schema states.

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

Conciseness3/5

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

Two sentences, the second of which retreads the first ('Get a specific script' / 'Gets details for a script specified by its ID'). Front-loaded correctly but wasteful, with no added value in the repetition.

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, so return values need not be explained, and the permission note is present. However, for a simple read tool the description omits any hint about output shape or how verbose/response_format change it, leaving it merely adequate.

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 all three parameters are documented in the schema, which sets the baseline at 3. The description adds no extra meaning about script_id format, the effect of verbose, or the markdown/json switch.

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?

Names a specific verb (Get) and resource (script) with an explicit retrieval key (ID), which distinguishes it from action1_list_scripts and action1_update_script. The second sentence largely restates the first, so it clarifies scope without adding sibling differentiation.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'specified by its ID' implies a lookup path versus listing, but the agent must infer that listing goes through action1_list_scripts.

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

Deploy Server