Skip to main content
Glama

workbuddy_create_cloud_task

Creates a WorkBuddy cloud task from a required prompt and optional name, dispatching it to a preconfigured model or agent profile for remote development work.

Instructions

Create a WorkBuddy cloud task. The public API does not expose a per-call model selector; use a preconfigured WorkBuddy model or agent profile.

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": {
      "prompt": "<prompt>"
    },
    "name": "workbuddy_create_cloud_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
promptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure for a write operation. It usefully discloses the model-selection constraint, but says nothing about what a 'cloud task' is, whether creation is async, what handle or ID comes back for later polling, permissions required, or cost/rate limits.

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 tight sentences with the operation front-loaded and no filler. The second sentence earns its place as a genuine caveat, though it slightly distracts from describing the inputs.

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

Completeness2/5

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

A mutation tool with no annotations, no output schema, and 0% parameter coverage needs substantially more: what is returned on success, how to track the task afterwards, and what the two inputs mean. None of that is present.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must compensate and does not: neither 'name' nor 'prompt' is explained, and there is no guidance on prompt content, length, or whether name is an identifier or a label. The only adjacent hint is that model choice is not a parameter.

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 first sentence states a specific verb and resource: 'Create a WorkBuddy cloud task.' An agent immediately knows the operation. It stops short of distinguishing this from plausible siblings such as workbuddy_start_development, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

The second sentence gives a real constraint (no per-call model selector; use a preconfigured model or agent profile), which implies when this tool is usable. But there is no explicit when-to-use/when-not guidance and no routing to an alternative such as workbuddy_start_development or how to follow up with workbuddy_status.

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