Skip to main content
Glama

submit_task

Queues a coding task for an isolated worker with optional spec.context for requirements and decisions; project context and documents freeze automatically. Returns without waiting.

Instructions

Queue a coding task; optional spec.context supplies requirements_summary, design_decisions, constraints and document paths. Project context and documents are frozen automatically. Worker must be running separately. Does not wait for completion.

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": {
      "spec": "<spec>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "submit_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses important traits such as asynchronous execution, automatic freezing of project context and documents, and the separate worker prerequisite, but it omits idempotency behavior, duplicate-key handling, permissions, and what the call returns.

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?

The description is compact and front-loaded, with the core action stated first and supporting constraints following in short sentences. Every sentence adds useful information without repetition.

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?

For a tool with no annotations, no output schema, 0% schema description coverage, and a nested spec object, the description is incomplete. It covers key async and freezing behavior but omits idempotency semantics, expected return information, and error or duplicate-submission behavior.

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%, so the description must compensate. It explains that spec.context can supply requirements_summary, design_decisions, constraints, and document paths, but it leaves the required idempotency_key completely unexplained and does not describe the top-level spec object beyond the optional context field.

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 specific verb and resource: queue a coding task. It also clarifies that the operation is asynchronous and does not wait for completion, though it does not explicitly differentiate itself from siblings like revise_task or submit_review.

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?

It gives useful context that a worker must be running separately and that the call does not wait for completion. However, it does not say when to use this versus revise_task, submit_review, or other task-related siblings, so usage guidance is implied rather than explicit.

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