MyClawn Computer

See what the computer is doing

myclawn_desktop_activity

Read-onlyIdempotent

Shows the latest task's steps on the MyClawn computer (pages opened, clicks, notes along the way) and whether it is still running. Use it to check on a long task, after myclawn_desktop_run reported it is still working, or when the user asks how it is going. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`steps`	Yes
`title`	Yes
`running`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 28, 2026

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```
addedOutput schema / properties / steps / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / steps / items / properties

Added value: +{
+  "at": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "kind": {
+    "type": "string"
+  },
+  "status": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "text": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / steps / items / required

Added value: +[
+  "kind",
+  "text",
+  "status",
+  "at"
+]

addedOutput schema / properties / steps / items / type
```
Added value: +"object"
```

addedOutput schema / properties / title

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "steps"
-]New value: +[
+  "title",
+  "running",
+  "steps"
+]

First observedSep 28, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the trailing 'Read-only.' adds little. What the description does add is behavioral scope beyond the annotations: it only covers the LATEST task (not history), and it reports both step detail and running state. That is useful disclosure, though nothing about freshness, staleness, or limits of the step list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned and backed by when-to-use conditions; nothing is buried. The only waste is the terminal 'Read-only.', which merely restates readOnlyHint=true already present in annotations.

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?

With an output schema present, the description need not describe return values, and with zero params there is no parameter burden, so the description is sufficient to invoke correctly. The remaining gap is sibling disambiguation against myclawn_desktop_status and myclawn_desktop_tasks, which an agent choosing between near-identical status-style tools would want resolved.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. It correctly signals the scope is fixed to 'the latest task' rather than requiring any selector, which is the only semantic point worth noting.

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?

The description states a concrete verb and resource ('Shows the latest task's steps on the MyClawn computer') and enumerates the content returned (pages opened, clicks, notes), plus a liveness check. It is clear on its own, but it does not differentiate itself from the closely related siblings myclawn_desktop_status and myclawn_desktop_tasks, which sound like they could also report task state.

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 gives explicit triggering conditions: checking a long task, following up after myclawn_desktop_run reported work in progress, or when the user asks how it is going. That is strong when-to-use guidance naming a sibling. It stops short of any when-not guidance or comparison against myclawn_desktop_status/tasks, which is the main ambiguity an agent would face.

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

All MyClawn Computer tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?