Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Stop Automation Session

stop_automation_session
Destructive

Stop an active automation session for configuration import or export by providing its session ID, ending a transfer started by import_configuration or export_configuration.

Instructions

Stop an automation (import/export) session started by import_configuration or export_configuration.

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": {
      "session_id": "<session_id>"
    },
    "name": "stop_automation_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds only which session kinds are affected; it says nothing about what stopping actually does to an in-progress import/export (partial state, rollback, cleanup) or why a second call behaves differently given non-idempotency.

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?

A single front-loaded sentence with no filler; the resource scope and originating tools are stated immediately.

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

Completeness2/5

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

An output schema covers return values, but for a destructive, non-idempotent stop operation with an unexplained `confirm_token`, the definition is too thin. An agent cannot determine confirmation requirements or the consequence of stopping mid-operation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden and does not. In particular the `confirm_token` parameter is undocumented anywhere and its purpose, format, and when it is required are entirely unexplained.

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 (stop) and a scoped resource (automation import/export sessions), and even names the sibling tools that create such sessions. It does not distinguish itself from the sibling `stop_session`, leaving ambiguity about which session types go where.

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 reference to `import_configuration`/`export_configuration` implies the context in which this tool applies, but there is no explicit when-to-use versus `stop_session` or `stop_task`, and no prerequisite or sequencing guidance.

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