Skip to main content
Glama

manage-project-workflow

Handle project phases, milestones, tasks, and allocations. Manage scheduling, task dependencies, and resource allocation for efficient project workflow.

Instructions

Consolidated tool for managing project workflow entities (phases, milestones, project-tasks, allocations). Handles all project-specific operations including scheduling, task management, and resource allocation through a decision-tree approach.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe entity ID (phase_id, milestone_id, project_task_id, or task_id for allocations)
dateNoMilestone date (YYYY-MM-DD)
nameNoName/title of the entity
pageNoPage number for pagination
colorNoColor (hex code)
hoursNoAllocated hours
notesNoNotes or description
activeNoActive status (0=archived, 1=active)
budgetNoTask budget
formatNoResponse format - either "json" or "xml"json
statusNoStatus code
billableNoBillable flag (0=non-billable, 1=billable)
end_dateNoEnd date (YYYY-MM-DD)
per-pageNoNumber of items per page (max 200)
phase_idNoFilter by phase ID
priorityNoPriority level (1-5)
completedNoCompletion status (0=incomplete, 1=complete)
operationYesThe workflow operation to perform
people_idNoFilter by person ID
task_typeNoTask type
created_byNoUser ID who created the milestone
project_idNoFilter by project ID
repeat_endNoRepeat end date
sort_orderNoSort order
start_dateNoStart date (YYYY-MM-DD)
task_namesNoTask name/title
task_orderNoArray of task IDs with new sort orders
budget_typeNoBudget type
descriptionNoMilestone description
entity_typeYesThe type of workflow entity (phases, milestones, project-tasks, allocations)
modified_byNoUser ID who last modified
budget_totalNoTotal budget
dependenciesNoTask dependencies
non_billableNoNon-billable flag (0=billable, 1=non-billable)
repeat_stateNoRepeat state
project_tasksNoArray of project tasks for bulk creation
reminder_dateNoReminder date
reminder_sentNoReminder sent flag (0=not sent, 1=sent)
completed_dateNoCompletion date
estimated_hoursNoEstimated hours
default_hourly_rateNoDefault hourly rate
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It mentions a 'decision-tree approach' but does not explain what that entails, side effects, authentication needs, or how operations affect state. The tool has 41 parameters and 18 operations, yet the description lacks behavioral context.

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 a single sentence that efficiently conveys the tool's purpose and entity scope. While concise, it could be improved by front-loading key usage guidance.

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's complexity (41 parameters, 18 operations, 4 entity types, no output schema, no annotations), the description is insufficient. It does not explain how parameters relate to operations, what responses look like, or how to construct valid requests.

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% with detailed parameter descriptions (e.g., 'The entity ID (phase_id, milestone_id, project_task_id, or task_id for allocations)'). The description does not add additional parameter-level meaning, so it merits a baseline 3 for compensating schema coverage.

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 clearly states it's a consolidated tool for managing four workflow entity types (phases, milestones, project-tasks, allocations) and mentions scheduling, task management, and resource allocation. However, it does not distinguish itself from the many sibling tools that handle specific operations for each entity, leaving ambiguity about when to use this tool over those.

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?

The description provides no guidance on when to use this consolidated tool versus the many existing per-entity tools (e.g., create-phase, list-phases, update-milestone). No when-not-to-use or alternative recommendations are given.

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