Skip to main content
Glama

Get automation

get_automation
Read-only

Every setting and message of one automation.

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
idYesAutomation id from list_automations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered structurally. The description adds one useful behavioral fact beyond that: the response is exhaustive ('every setting and message'), telling the agent to expect a full object rather than a summary. It says nothing about whether missing automations error or return null, but for a simple read that is a modest gap.

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?

Extremely short with no wasted words, but it is a bare fragment rather than a front-loaded sentence, and the missing verb pushes interpretation onto the name and annotations. Conciseness is achieved at the cost of clarity.

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 single-parameter read tool with annotations and no output schema, the description does the minimum: it signals that the full payload is returned. It does not cover error behavior or how the result differs from a listed summary, leaving small but real gaps.

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?

One parameter with 100% schema description coverage, including UUID format and an explicit provenance hint ('Automation id from list_automations'). The description adds no additional meaning about the id, which is acceptable given the schema does the work.

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

Purpose3/5

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

The phrase 'Every setting and message of one automation' conveys that this returns the full detail of a single automation, which is meaningfully distinct from list_automations. However, it is a noun fragment with no verb, so the agent must infer 'retrieve' from the tool name and readOnlyHint rather than reading it in the description.

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?

No guidance on when to use this versus list_automations (which presumably returns summaries) or get_stats. The schema's id description points back to list_automations, but that routing hint lives in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources