Skip to main content
Glama

task_create

DestructiveIdempotent

Create a project with a title, request, and requirements, using requirement IDs and descriptions; set kind='archive' for ZIP deliverables or kind='file' for other files.

Instructions

Create a project from original words and deliverables. Each requirement needs id and description; use kind='archive' for an exported ZIP, otherwise kind='file'.

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>",
      "request": "<request>",
      "requirements": "<requirements>",
      "op_id": "<op_id>"
    },
    "name": "task_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoresearch
op_idYes
titleYes
requestYes
constraintsNo
requirementsYes
policy_sourceNouser request

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description does not explain what destructive behavior occurs, how op_id provides idempotency, or what side effects creation has. It only states a structural requirement about requirement objects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with no filler wording. However, the second sentence contains incorrect parameter guidance about 'kind' that undermines its usefulness.

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?

This is a 7-parameter write tool with no schema descriptions, and the description is far too thin to guide correct invocation. The output schema may cover return values, but usage guidance and most parameter semantics are missing.

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?

With 0% schema description coverage, the description should compensate, but it only briefly describes the requirements array and references a 'kind' parameter that does not exist in the schema. It leaves title, request, mode, op_id, constraints, and policy_source entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Create a project from original words and deliverables,' which is vague and mismatched with the tool name task_create. It does not clearly state what kind of task is created or distinguish the tool from sibling task_* tools.

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

Usage Guidelines2/5

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

There is no guidance on when to use task_create versus alternatives such as task_update, task_get, or task_list. The only conditional statement concerns an unsupported 'kind' parameter, not tool selection.

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