Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Automation

get-automation
Read-onlyIdempotent

Retrieve one automation's latest steps and connections in create/update-accepted format, plus issues left before it can be enabled.

Instructions

Get one automation: its latest steps and connections, in the format create-automation and update-automation accept, and the issues left before it can be enabled.

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": {
      "id": "<id>"
    },
    "name": "get-automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe automation id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it returns the latest version of steps/connections in a write-compatible shape and surfaces `issues` gating enablement. It does not mention error behavior for unknown ids or whether drafts vs published automations are returned, so it only modestly exceeds the annotation baseline.

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?

One sentence, front-loaded with the verb and resource, then the return contents. No filler, no restatement of the title.

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?

For a one-parameter read tool with full annotation coverage, this is close to sufficient. But with no output schema, the description should ideally say more about the shape of `steps`/`connections`/`issues` (e.g. whether they are lists, and what an empty or disabled automation returns).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema description coverage, the schema already carries the burden ('The automation id', plus uuid format and pattern). The description adds nothing parameter-specific, but the baseline for full coverage with 0-1 params is a 4.

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 ('Get one automation') and immediately enumerates what is returned: latest `steps`, `connections`, and remaining `issues`. This is far more informative than a bare 'Get Automation' restatement, though it does not explicitly contrast itself with the sibling get-automation-run or list-automation-runs.

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?

The description implies usage by naming create-automation and update-automation as the consumers of the returned format — an agent can infer this is a read-before-write/read-before-clone call. However, it never states when to use this versus get-automation-run or list-automation-runs, and gives no exclusions or prerequisites.

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

Deploy Server

Other Tools