Skip to main content
Glama

stop

Terminates one MCP-owned JsMacros task or all MCP tasks when no task is specified, running registered cleanup and releasing held keys when all are ended.

Instructions

Stop one MCP-owned JsMacros task, or all MCP tasks when task is omitted. Runs cleanup registered with mcp.track for the stopped tasks. Stopping all tasks also releases keys held in JsMacros.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that cleanup registered with mcp.track runs and that stopping all tasks releases JsMacros-held keys, but it does not cover error handling, permissions, return behavior, or whether stopping is reversible.

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?

The description is three tight sentences with the primary action and omission rule front-loaded. Every sentence adds information about scope, cleanup, or key release without repetition.

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 simple one-parameter tool without an output schema, it covers the core stopping semantics and side effects well. It remains incomplete about result reporting, failure cases, and identifier format, which an agent would need to invoke it confidently.

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 one optional parameter at 0% description coverage, so the description must compensate. It explains the key omission semantics but does not clarify what format the task identifier takes, such as a name, ID, or exact-match string.

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?

The description uses a specific verb and resource: stopping MCP-owned JsMacros tasks. It clearly distinguishes between stopping one task and stopping all tasks when the optional task parameter is omitted.

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

Usage Guidelines4/5

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

It clearly explains the single-task versus all-task behavior through parameter omission, which gives the agent a concrete usage rule. It does not explicitly compare against siblings like execute or mention when stopping would be inappropriate, but the context is clear.

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