Skip to main content
Glama

NoMac

by app.nomac
OverviewDiscussionsAdmin

Stop a command on a Mac

cancel_mac_job
Destructive

Stops a running command and everything it started: SIGTERM, a second, then SIGKILL. It comes back exited with reason cancelled, its output so far still readable; a command that already ended comes back unchanged (cancelled: false). For a hung build, an endless test run or a server no longer needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesCommand job ID (job_…) returned by exec_mac.
session_idNoMac session ID (ses_…). Optional: without it, the account's running Mac.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / session_id / description
      Previous value: -"Mac session ID (ses_…) returned by start_mac or list_mac_sessions."New value: +"Mac session ID (ses_…). Optional: without it, the account's running Mac."
    • changedInput schema / required
      Previous value: -[
-  "session_id",
-  "job_id"
-]New value: +[
+  "job_id"
+]
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": {},
-  "description": "The JSON response of the NoMac API for this operation",
-  "properties": {
-    "error": {
-      "additionalProperties": {},
-      "description": "Present only when the call failed",
-      "properties": {
-        "code": {
-          "description": "Stable machine-readable error code, for example insufficient_credit",
-          "type": "string"
-        },
-        "message": {
-          "description": "What went wrong and what to do next",
-          "type": "string"
-        }
-      },
-      "required": [
-        "code",
-        "message"
-      ],
-      "type": "object"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true and idempotentHint=false; the description goes well beyond them by disclosing the exact escalation (SIGTERM, a one-second grace, then SIGKILL), the resulting state (exited/cancelled), that partial output remains readable, and the no-op case for an already-finished command.

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?

Two tight sentences with zero filler, and the most decision-relevant fact (what gets killed and how) is front-loaded.

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?

With no output schema, the description compensates by describing the return state ('comes back exited with reason cancelled', 'cancelled: false'), and it covers the destruction semantics an agent needs before firing a destructive call.

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 description coverage is 100%, so job_id and session_id are already fully documented in the schema; the description adds no further parameter meaning (e.g., session scoping rules). Baseline 3 applies when the schema carries the load.

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 ('Stops a running command and everything it started') and scopes the blast radius to the process tree, which clearly separates it from exec_mac and get_mac_job among the siblings.

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?

Gives concrete when-to-use conditions: 'For a hung build, an endless test run or a server no longer needed.' It does not name an alternative tool or state when not to cancel, but the trigger scenarios are clear enough to route the agent.

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

All NoMac toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources