MyClawn Computer

List past tasks

myclawn_desktop_tasks

Read-onlyIdempotent

Lists the tasks the MyClawn computer has run, newest first, with each task's title, when it last changed and its state (done, or still running). Use it when the user asks what the computer did earlier or whether a job finished. Read-only; returns an empty list when the computer is not set up or not running.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tasks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

addedOutput schema / properties / tasks / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / tasks / items / properties

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

addedOutput schema / properties / tasks / items / required

Added value: +[
+  "title",
+  "state",
+  "updated_at"
+]

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

First observedSep 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is not carrying that burden. It adds genuine value beyond them by disclosing ordering (newest first) and the edge case of an empty list when the computer is not set up or running.

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 tight sentences with purpose and ordering front-loaded, followed by usage and then the edge case. Every sentence carries distinct information and nothing is redundant.

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?

For a read-only, zero-parameter listing tool with an output schema and full annotation coverage, this covers purpose, trigger, ordering, and the empty-list edge case. An agent has everything needed to select and call it; the output schema handles return values.

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 and schema coverage is 100%, so there is nothing for the description to compensate for; the 0-parameter baseline applies. There is no filtering or pagination parameter to explain.

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?

States a specific verb and resource ('Lists the tasks the MyClawn computer has run') plus ordering ('newest first') and the returned fields. It conceptually separates itself from activity/status siblings, but never names an alternative tool, so the distinction is inferred rather than explicit.

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 a clear trigger: 'Use it when the user asks what the computer did earlier or whether a job finished.' That is actionable context, but there are no exclusions and no routing to myclawn_desktop_activity or myclawn_desktop_status, which look adjacent.

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

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?