Skip to main content
Glama

create-project-task

Create a task in a Float project by providing project ID and task name. Optionally include phase, notes, budget, priority, dependencies, and status to organize project work.

Instructions

Create a new project task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
task_namesYesTask name/title
phase_idNoPhase ID (if assigning to a specific phase)
notesNoTask notes
budgetNoTask budget (if setting budget at task level)
budget_typeNoBudget type (1=hours, 2=amount, etc.)
colorNoTask color (hex code)
billableNoBillable flag (0=non-billable, 1=billable)
activeNoActive status (1=active, 0=archived)
priorityNoTask priority (1=low, 2=medium, 3=high, etc.)
sort_orderNoSort order within project
dependenciesNoArray of project task IDs this task depends on
estimated_hoursNoEstimated hours for completion
statusNoTask status (numeric)
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. The single sentence only states it creates a task, but it doesn't mention side effects, permission requirements, rate limits, or what happens on success/failure. For a mutation tool, this is insufficient.

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 extremely concise, consisting of a single sentence with no wasted words. However, it lacks structural elements like bullet points or emphasis on key constraints. It is efficient but could be more informative without losing brevity.

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?

Given the tool has 14 parameters (many optional) and no output schema, the description should provide more context about default behaviors, constraints, or return values. The minimal description leaves the agent guessing about what happens when optional fields are omitted.

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?

The input schema has 100% description coverage, so the schema already documents all parameters. The description adds no additional meaning beyond what the schema provides. Baseline of 3 is appropriate since the description doesn't detract but also doesn't enhance understanding.

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 'Create a new project task' clearly states the verb (create) and resource (project task), making the basic purpose obvious. However, it does not distinguish this tool from sibling tools like 'create-task' or 'bulk-create-project-tasks', which could cause confusion. It is clear but not differentiated.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. For example, it doesn't clarify if this is for creating a single task vs. bulk creation.

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/asachs01/float-mcp'

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