Skip to main content
Glama

task_create

Create a task for an agent to pick up, with title, description, outcome, priority, and tags. Avoid duplicates by checking task list first.

Instructions

Create a task for yourself or another agent to pick up.

Use when there's a discrete unit of work that should be tracked, may be done by a different agent, or needs to survive across sessions. Check task_list() for duplicates before creating.

Args: title: Short imperative description, e.g. "Fix auth token expiry bug". description: Context, acceptance criteria, or relevant links. expected_outcome: What done looks like — specific, observable result. project: Project scope. Defaults to MCP_PROJECT if set. priority: low, normal (default), or high. tags: Labels for filtering, e.g. ["writing", "infra"].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesShort imperative description, e.g. "Fix auth token expiry bug".
descriptionNoContext, acceptance criteria, or relevant links.
expected_outcomeNoWhat done looks like — specific, observable result.
projectNoProject scope. Defaults to MCP_PROJECT if set.
priorityNolow, normal (default), or high.normal
tagsNoLabels for filtering, e.g. ["writing", "infra"].

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations (destructiveHint: false, openWorldHint: false) are consistent. Description adds context about task being trackable and cross-session, but no further behavioral traits disclosed.

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?

Description is front-loaded with purpose, then usage guidance, then Args list. Well-structured but slightly verbose; could condense Args repetition.

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?

Covers usage, parameters, and hints. With output schema present, return values not needed. Missing potential prerequisites or side effects, but adequate for creation tool.

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?

Schema coverage 100% with descriptions. The description repeats most parameter information with slight elaboration (examples, defaults). Adds marginal value beyond schema.

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

Purpose5/5

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

Description starts with clear verb+noun: 'Create a task for yourself or another agent to pick up.' Differentiates from sibling tools like task_list, task_update. Advises checking for duplicates, reinforcing its purpose.

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

Usage Guidelines5/5

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

Explicitly states when to use: discrete unit of work, may be done by different agent, or needs to survive sessions. Also suggests checking task_list for duplicates before creating.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NicolasPrimeau/artel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server