Organize with AI (OwAI)

Get library command status

get_library_command

Read-onlyIdempotent

Read the status and result of an existing OwAI library operation on its owner. Does not emit or execute shell commands. wait_ms=0 returns immediately; pending/running is not completion, and completed results include per-item failures.

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": {
      "command_id": "<command_id>"
    },
    "name": "get_library_command"
  }
}

Input Schema

Name	Required	Description	Default
`wait_ms`	No
`command_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes
`command`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / command_id / maxLength
```
Added value: +200
```

changedOutput schema / properties / command / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "attempt": {
-        "type": "number"
-      },
-      "claimed_at": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "completed_at": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "device_id": {
-        "type": "string"
-      },
-      "error": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "id": {
-        "type": "string"
-      },
-      "kind": {
-        "type": "string"
-      },
-      "payload": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "requested_at": {
-        "type": "number"
-      },
-      "result": {
-        "anyOf": [
-          {
-            "additionalProperties": {},
-            "propertyNames": {
-              "type": "string"
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "status": {
-        "enum": [
-          "pending",
-          "running",
-          "succeeded",
-          "failed"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "device_id",
-      "kind",
-      "payload",
-      "status",
-      "attempt",
-      "requested_at",
-      "claimed_at",
-      "completed_at",
-      "result",
-      "error"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "attempt": {
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "claimed_at": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "completed_at": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": 0,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "device_id": {
+        "type": "string"
+      },
+      "error": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "kind": {
+        "type": "string"
+      },
+      "payload": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "requested_at": {
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "result": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "status": {
+        "enum": [
+          "pending",
+          "running",
+          "succeeded",
+          "failed"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "device_id",
+      "kind",
+      "payload",
+      "status",
+      "attempt",
+      "requested_at",
+      "claimed_at",
+      "completed_at",
+      "result",
+      "error"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 20, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent), yet the description adds genuinely non-obvious behavior: wait_ms=0 returns immediately, pending/running status does not mean the operation finished, and completed results can still contain per-item failures. That last point is a critical caveat an agent could not infer from annotations or schema.

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?

Three short sentences, purpose front-loaded, then the disambiguation, then the operational semantics. Every clause earns its place with no padding or repetition of schema/annotation data.

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

Completeness4/5

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

An output schema exists so return-shape explanation is unnecessary, and the description supplies the polling and partial-failure semantics an agent needs. It is slightly thin on failure modes, e.g. what happens with an unknown or expired command_id.

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 0%, so the description carries the full burden. It meaningfully explains wait_ms (0 = immediate return, implying blocking otherwise) but omits the default of 15000 and the 20000 cap, and says nothing about command_id beyond implying it identifies the operation.

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 — 'Read the status and result of an existing OwAI library operation' — and immediately preempts the most likely misreading of the name by noting it does not emit or execute shell commands. An agent can tell this is a polling/status tool for a previously started job, not a command executor.

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?

The phrase 'an existing OwAI library operation' makes clear this is for polling something already started, and the wait_ms note gives operational context for when to block vs. return immediately. No alternative sibling or explicit 'when not to use' is named, so it stops short of a full 5.

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

All Organize with AI (OwAI) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?