Skip to main content
Glama

NoMac

by app.nomac
OverviewDiscussionsAdmin

Get Mac command status

get_mac_job
Read-only

Returns a command's state (running, exited or failed) and exit code, and once it has ended its stdout and stderr (first 64 KiB each, with a cursor when more follows). stream with cursor reads a chunk from any point, also while it runs. wait_seconds (up to 40) waits for it to end, so one call replaces a polling loop. It never runs the command again. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoByte offset to read from: next_cursor of the last read (default 0)
job_idYesCommand job ID (job_…) returned by exec_mac.
streamNoRead this stream as a chunk from cursor, also while the command runs
session_idNoMac session ID (ses_…). Optional: without it, the account's running Mac.
wait_secondsNoWait up to this long (0-40) for a running command to finish, instead of polling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Byte offset to read from: next_cursor of the last read (default 0)",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / stream
      Added value: +{
+  "description": "Read this stream as a chunk from cursor, also while the command runs",
+  "enum": [
+    "stdout",
+    "stderr"
+  ],
+  "type": "string"
+}
  2. 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"
+]
  3. 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
  4. Changed1 schema field changed
    • addedInput schema / properties / wait_seconds
      Added value: +{
+  "description": "Wait up to this long (0-40) for a running command to finish, instead of polling.",
+  "maximum": 40,
+  "minimum": 0,
+  "type": "integer"
+}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds real behavioral context beyond that: 64 KiB truncation per stream, a cursor returned when more data follows, the 40s wait cap, and the guarantee it will not re-run the command. It omits details like ordering/consistency of stream reads, keeping it short of 5.

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?

Dense but front-loaded: state/exit code/streams come first, then the cursor and wait mechanics, then the read-only guarantee. Every sentence carries distinct information with no padding.

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?

No output schema exists, so the description correctly explains what is returned (state, exit code, stdout/stderr, cursor). Combined with the annotations covering the safety profile and the 100% schema coverage, an agent has everything needed to call 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%, so all five parameters are already documented in the schema. The description reinforces cursor/stream/wait_seconds behavior and adds the nuance that streaming works 'also while it runs,' but adds little beyond the schema's own parameter text. Baseline 3 applies.

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: returns a command's state (running, exited, failed), exit code, and stdout/stderr. An agent can immediately distinguish it from exec_mac (which runs commands) because the description explicitly says it never runs the command again.

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?

Explains the two usage modes clearly: stream+cursor to read chunks (even while running) and wait_seconds to avoid a polling loop. It also clarifies the read-only, non-re-executing nature. It stops short of naming alternative sibling tools (e.g. cancel_mac_job) or exclusions, so not a 5.

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