Skip to main content
Glama
AmrDab

ClawdCursor

by AmrDab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task

Destructive

Hand ClawdCursor a whole natural-language desktop instruction and let its internal agent loop execute, decompose, and return a trace. It pauses for sign-in, 2FA, or CAPTCHA and can resume or abort.

Instructions

Requires the clawdcursor agent daemon to be running (binds 127.0.0.1:3847 with an LLM configured). Hand clawdcursor a WHOLE natural-language task and let its internal agent loop execute it (accessibility first, screenshots when the screen has no readable structure). Use this when you don't want to micromanage every primitive — clawdcursor decomposes the task, picks the cheapest execution path, and returns a trace. BOUNDED-SYNC: waits up to timeout seconds (default 45) — a longer task returns {status:"running"} with progress while it CONTINUES in the background; re-call with the SAME instruction to keep waiting (re-attaches, never restarts), {action:"status"} to poll, {action:"abort"} to stop it. At a roadblock (sign-in, 2FA, CAPTCHA, a step it may not take) the task PAUSES for the user and returns {status:"paused", waitingFor}: keep re-calling to wait, never restart; {action:"resume"} if the user tells you they finished. The computer/accessibility/window/system/browser compounds are for when you want step-level control yourself. If the daemon isn't running you get a clear error telling you how to start it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoDefault "run" (submit/continue the instruction). "status" → poll the running task (cheap, poll at 1–2 Hz). "abort" → stop the running task. "resume" → continue a task paused for the user, when they tell you they finished.
timeoutNoMax seconds to WAIT for completion before returning a running receipt (default 45, clamped 1–50). The task keeps running — this only bounds the wait.
instructionNoNatural-language task description, e.g. "open Notepad and type hello", "go to github.com", "send email in Outlook". Required for action "run" (the default); ignored for status/abort.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.16

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the hard prerequisite (daemon on 127.0.0.1:3847 with an LLM configured), the bounded-sync wait semantics and its default, that a timed-out task continues in the background rather than restarting, and that roadblocks (sign-in, 2FA, CAPTCHA) cause a pause with `waitingFor`. These are exactly the traits an agent needs and none are in the annotations.

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?

Front-loads the daemon prerequisite, then purpose, then protocol, using bold caps to mark the load-bearing clauses. It is long, but every sentence carries distinct operational information; the density is warranted by the tool's complexity.

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, yet the description compensates by naming the return shapes ({status:"running"} with progress, {status:"paused", waitingFor}) and the daemon-error path. Combined with the protocol for continuing, polling, and aborting, an agent has everything required to call and recover from this tool.

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 the enum actions, timeout bound, and instruction requirement are already documented. The description reinforces the same facts (default 45s, clamp, ignored for status/abort) but adds no syntax or semantics beyond the schema, making the baseline 3 appropriate.

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+resource: hand a whole natural-language task to clawdcursor's internal agent loop, which decomposes it and picks the cheapest execution path. It explicitly contrasts with the step-level `computer`/`accessibility`/`window`/`system`/`browser` siblings, so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use trigger ("when you don't want to micromanage every primitive") and names the alternatives plus their role (step-level control). It also spells out the operating protocol under failure: re-call with the same instruction to keep waiting, poll with status, abort, or resume.

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

Deploy Server

Other Tools