Skip to main content
Glama

Create Task

create_task

Create tasks with team or private scope, assign to humans or AI, set due dates and priorities, and link to customers, contacts, or other entities.

Instructions

Create a new task. Scope 'org' (default) is visible to all team members; 'personal' is private to the creator. Use assigned_to with a FOUNDERS_OS_USER_ID for human assignment, or '@claude' / '@gpt' for AI assignment. Optionally link to any FounderOS entity (customer, contact, transaction, etc.) at creation time. If the response contains a conflict field, the task was NOT created. Present all options to the user using an interactive chooser (AskUserQuestion) if available, then retry with the selected date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags for filtering and grouping (e.g. ['Q2', 'fundraising']).
linksNoEntities to link this task to at creation time.
scopeNo'org' (default) for team-visible; 'personal' for private.
titleYesWhat needs to be done.
statusNoTask status. Defaults to 'todo'.
due_dateNoDue date (YYYY-MM-DD).
priorityNoPriority level. Defaults to 'medium'.
assigned_toNoWho to assign this to. Use a FOUNDERS_OS_USER_ID for a human, or '@claude' / '@gpt' for AI. A task takes exactly one assignee by design: the single accountable owner, the 'one neck to grab' (ONTG). This is deliberate, not a limitation - work split across several names tends to get done by no one. If several people are involved, still set one owner here and name the others in the description (or tag people you are waiting on with an @person tag).
descriptionNoAdditional details or context.
due_date_dayNoExpected day of the week for due_date. If provided, the server validates it matches. Catches errors when converting 'due Thursday' to a date. Mismatch returns the correct day and nearby alternatives.
blocked_reasonNoRequired context when status is 'blocked'.
blocked_by_task_idNoUUID of a task that blocks this one. Sets status to 'blocked' automatically if not already set.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses scope defaults, assignment rules, linking behavior, and conflict response. It explains design rationale for single assignee. However, it doesn't mention auth requirements or rate limits.

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 relatively concise for its detail, front-loading the main purpose. Each sentence adds value, though it could be more structured. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description omits the full response structure (e.g., returned task object with ID). It only mentions 'conflict' field. For a create tool with no output schema, this is a gap. Parameter coverage is good, but output missing.

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 100%, baseline 3. The description adds value by explaining the single-assignee philosophy, due_date_day validation, and blocked_by_task_id auto-status. It provides extra context beyond the 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?

The description explicitly states 'Create a new task' and elaborates on scope, assignment, and linking. It uses a specific verb and resource, clearly distinguishing from siblings like update_task or assign_task.

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

Usage Guidelines4/5

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

The description provides clear guidance on when and how to use the tool, including scope options, assignment formats, linking, and conflict handling. It does not explicitly list alternatives but the context is clear.

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/OurThinkTank/founders-os'

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