Skip to main content
Glama

update-project-task

Update an existing project task by providing its ID and modifying fields like name, project, phase, notes, budget, billable, active, priority, dependencies, estimated hours, or status.

Instructions

Update an existing project task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_task_idYesThe project task ID
task_namesNoTask name/title
project_idNoProject ID
phase_idNoPhase ID
notesNoTask notes
budgetNoTask budget
budget_typeNoBudget type
colorNoTask color (hex code)
billableNoBillable flag (0=non-billable, 1=billable)
activeNoActive status (1=active, 0=archived)
priorityNoTask priority
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 provided, so description carries full burden. Only confirms mutation ('update') but does not disclose side effects, error behaviors, or permissions required.

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?

Extremely concise one-sentence description, but sacrifices necessary detail. Could be improved with structured information.

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?

With 15 optional parameters and no output schema, the description fails to explain return values, optionality, or valid parameter combinations.

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 is 100%, so parameters are already described in schema. The description adds no additional meaning or constraints.

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?

Description clearly states the verb 'Update' and resource 'existing project task', distinguishing it from siblings like archive-project-task or delete-project-task. However, it lacks specificity about which fields can be updated.

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 on when to use this tool versus alternatives such as archive-project-task or reorder-project-tasks. No prerequisites or context provided.

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