Skip to main content
Glama

create-project-task

Create a new task within a Float project, specifying details like name, phase, budget, priority, and dependencies 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?

No annotations are provided, so the description carries full burden. It states 'Create a new project task', implying a write operation, but doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens on failure, or the response format. This is a significant gap for a mutation tool with no annotation coverage.

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?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, stating the core purpose without unnecessary elaboration, making it easy to parse quickly.

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 complexity (14 parameters, mutation operation) and lack of annotations and output schema, the description is incomplete. It doesn't address key aspects like what the tool returns, error handling, or usage context, leaving the agent with insufficient information for reliable invocation.

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 description coverage is 100%, so the schema fully documents all 14 parameters. The description adds no parameter information beyond what's in the schema, such as explaining relationships between parameters (e.g., how 'budget' and 'budget_type' interact). Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/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'), but it's generic and doesn't distinguish from sibling tools like 'create-task' or 'bulk-create-project-tasks'. It specifies the resource type but lacks detail about scope or differentiation.

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 guidance is provided on when to use this tool versus alternatives such as 'create-task' (general task creation) or 'bulk-create-project-tasks' (multiple tasks). The description offers no context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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