Radar noEixo

Get automation

get_automation

Read-only

⚡ AUTOMAÇÕES (event-triggered) — Retorna o detalhe completo de UM fluxo de automação, incluindo o array de "actions" já parseado (list_automations não traz actions, só resumo). É a fonte do array atual quando só parte das ações vai mudar: update_automation substitui o array inteiro, e ações que não forem reenviadas deixam de existir (ex.: reescrever só o texto de um send_whatsapp apaga um send_to_ekyte/add_contact_tag que vinha depois, se ele não for reenviado).

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": {
      "automation_id": "<automation_id>"
    },
    "name": "get_automation"
  }
}

Input Schema

Name	Required	Description	Default
`automation_id`	Yes	ID do fluxo a consultar (obtido via list_automations)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive nature. The description adds substantial context about what is returned (parsed actions array) and, crucially, warns that the array is the source of truth and must be fully resent during updates to avoid deleting actions. This is valuable behavioral insight beyond annotations, though it focuses on the update sibling rather than this tool's own operation.

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?

Front-loaded with an emoji and category label, then purpose and differentiation. The warning example is useful but slightly verbose, though every sentence contributes relevant information. Overall efficient, with minor room for trimming.

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

Completeness4/5

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

For a simple read tool with one parameter and annotations covering safety, the description adequately explains the return value (full detail with actions) and the key use case. It could mention other top-level fields or pagination, but given no output schema, the level of detail is sufficient for correct invocation.

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?

The schema has 100% description coverage, including that the ID is obtained via list_automations. The description does not add any parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 'Retorna' and resource 'detalhe completo de UM fluxo de automação', and explicitly distinguishes from list_automations by noting it returns the actions array while list only gives a summary. An agent can immediately tell this is the detailed-read variant.

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

Usage Guidelines5/5

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

Explicitly names the alternative list_automations and why to choose this tool (to get actions). Also explains the critical when-to-use scenario: when only part of the actions will change, because update_automation replaces the entire array. The guidance is precise and actionable.

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

All Radar noEixo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?