Timequip

Create task

create_task

Create a new task in a project. Status defaults to the first workflow column if omitted.

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

Input Schema

Name	Required	Description
`tags`	No	Tag names to attach (created if new).
`title`	Yes	Task title.
`status`	No	Workflow status name, e.g. "To Do".
`content`	No	Description as HTML.
`dueDate`	No	Due date, ISO 8601 (e.g. "2026-07-01").
`assignee`	No	Assignee, "@username" or email (must be an account member).
`priority`	No
`projectKey`	Yes	Project key, e.g. "ACME".

Output Schema

Name	Required	Description	Default
`task`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds one genuinely useful behavioral detail outside the annotations — that status falls back to the first workflow column when omitted. It says nothing about permissions or membership requirements for creating tasks.

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?

Two short sentences, both load-bearing: the first establishes the action and scope, the second covers the only non-obvious default. Nothing is repeated from the schema or the title.

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 creation tool with an output schema, well-documented parameters, and annotations covering the safety profile, the description is nearly sufficient. Remaining gaps — auth/membership requirements and whether tags are auto-created (left to the schema) — are minor.

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?

Schema coverage is 88%, so the baseline is 3, and the description earns a bump by documenting the defaulting behavior of the 'status' parameter, which the schema only describes as a workflow status name. It adds no further semantics (e.g. tag auto-creation, assignee constraints) beyond what the schema already carries.

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 ('Create a new task in a project'), which distinguishes it from create_project and update_task. It does not name siblings explicitly, so it stops short of the top score, but the purpose is unambiguous.

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?

Usage is only implied by the create semantics; there is no explicit when-to-use or when-not-to-use guidance, nor any routing to siblings like update_task or change_task_status. The status-default note hints at a prerequisite consideration but is not framed as guidance.

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

All Timequip 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.

Resources

Need Help?