Veynod

Create Task

create_task

Create a task for an agent role (EXECUTOR/ANALYST/AUDITOR).

project and repo are optional routing labels. Omit both for a task that is
not tied to a project or repository; a blank string is rejected.

acceptance [{id, text, kind: AUTO|MANUAL}] lists what the change is judged
against; it locks at the first claim and an approval must PASS every item.

Pass pointers, not copies: context_docs [{namespace, doc_key, version?}]
are pinned at the first claim and returned with it; done_definition and
output_to {namespace, doc_key | doc_key_pattern} say what done means and
where the result goes. assignee / required_role / required_capabilities
limit who may claim. mentions (agent:<id>, human:<id>) notify principals.

SCOUT is intentionally not claimable; raw collection work belongs in a
raw_inbox document. depends_on task keys create dependency links and keep
the new task TODO until every dependency is DONE. This mirrors REST
POST /v1/tasks.

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": {
      "title": "<title>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No		work
`repo`	No
`agent`	No
`title`	Yes
`status`	No		READY
`project`	No
`assignee`	No
`mentions`	No
`priority`	No
`task_key`	No
`namespace`	No
`output_to`	No
`acceptance`	No
`depends_on`	No
`description`	No
`max_retries`	No
`context_docs`	No
`assigned_role`	No
`input_context`	No
`required_role`	No
`done_definition`	No
`idempotency_key`	No	Optional. Retries with the same key and arguments within 24 h replay the first result (replayed=true) without a second write; a different body with the same key is idempotency_key_reused.
`session_batch_id`	No
`require_continuation`	No
`allow_missing_context`	No
`required_capabilities`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations only declare that this is a non-read-only, non-destructive operation. The description adds substantial lifecycle context: acceptance criteria lock at first claim, context_docs are pinned, dependencies keep the task TODO, and mentions notify principals.

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?

The description is dense but front-loads the core purpose and then groups parameter semantics logically. It is longer than a simple one-liner, but most sentences add meaningful operational context rather than filler.

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?

For a complex 26-parameter mutation tool, the description covers the most important lifecycle and routing behaviors, and an output schema exists so return values need not be explained. It remains incomplete for several optional control parameters, but the core creation semantics are well specified.

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?

With 26 parameters and only 4% schema description coverage, the description must carry most of the semantic burden. It explains key parameters such as acceptance, context_docs, output_to, assignee, required_role, and depends_on, but many others remain undocumented, including status, priority, kind, max_retries, and continuation-related flags.

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 clearly states a specific verb and resource: create a task for an agent role. It distinguishes the tool from generic task operations by naming the role scope, though it does not explicitly contrast with siblings such as create_subtasks.

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 exclusions, notably that SCOUT is not claimable and raw collection work belongs in a raw_inbox document. However, it does not explicitly compare this tool with create_subtasks, update_task, or other task-related siblings, so the when-to-use guidance is only implied.

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

All Veynod tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.