Skip to main content
Glama

Activate automation

activate_automation
Destructive

Turn an automation on, so tracked events start runs. With a live number it texts real people. With no from, a number approved for its category must exist or issues says what is missing; sender shows the numbers it will use.

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": "activate_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAutomation id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered; the description still adds real value by spelling out the consequence ('it texts real people') and by disclosing that a preflight validation result ('issues') and the effective senders ('sender') are returned. Minor deduction for referencing a `from` input that the schema does not accept.

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?

Three short sentences, front-loaded with the purpose and the real-world effect. The middle sentence is telegraphic ('a number approved for its `category` must exist or `issues` says what is missing') and requires a re-read, but nothing is padded.

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 one-parameter tool whose annotations already carry the safety profile and which has no output schema, the description covers purpose, the real-world side effect, preconditions for validation failure, and the fields returned on failure/selection. That is enough for an agent to invoke it correctly.

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% for the single `id` parameter, so the baseline is 3. The description adds no meaning about `id` itself and instead discusses a `from` field that does not exist in the input schema, which risks an agent trying to pass an unsupported argument.

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 and resource ('Turn an automation on') plus the immediate consequence ('tracked events start runs'), which cleanly separates it from pause_automation and get_automation. An agent knows exactly what state change this performs without opening the schema.

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 'so tracked events start runs' clause implies when the tool is relevant, but there is no explicit when-to-use/when-not guidance and no naming of alternatives such as pause_automation, test_automation, or preview_automation, which an agent would plausibly need to choose between before going live.

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.