get_invoice
ChatGPTRetrieves one invoice (client billing document) with line items, per-project amounts, linked time entry and expense IDs, payment methods, delivery emails, and PDF URL. Use list_invoices to find the invoice ID first. Use list_time_entries and list_expenses to inspect source records.
get_person
ChatGPTRetrieves detailed info for a single person including bio, contact details, links to the person in an external system (externalPersons: external system, external id, name, and URL), employment from and through dates (null when employment has no start or end), the dated site assignment series, full position history with allocations, time-offs, and working hours. Use list_people to find the person ID first. Use manage_person siteAssignments to change the site series. Use get_position for deeper position details. timeEntryLastSubmittedDate is the date through which their timesheet is submitted. Use submit_timesheet to submit it.
get_position
ChatGPTRetrieves a single position (person-to-project assignment) with its allocations (scheduled time blocks). Use list_positions to find the position ID first. Use manage_positions for assignment changes and manage_allocations for planned work blocks.
get_project
ChatGPTRetrieves one project (client engagement or internal initiative) with linked CRM deals, links to this project in an external system (externalProjects: external system, external id, name, and URL), positions, budgets, budget schedules, planned expenses, tasks, notes, rate cards, and summary financials. Use list_projects to find the project ID first. Use list_expenses for recorded spend details when a project has expenses.
get_timer
ChatGPTReads your running timer (a stopwatch that becomes a time entry when stopped). timer is null when none is running. Stop it with stop_timer, or start one with start_timer.
list_allocations
ChatGPTLists allocations (scheduled time blocks on positions). Use manage_allocations to create, update, move, confirm, tentative, resize, or remove them. Supports filtering by position, project, person, or date range.
list_clients
ChatGPTLists clients (companies you work for). Use list_clients to find client IDs before creating or filtering projects. Supports search, owner, tag, internal, and archived filters.
list_expenses
ChatGPTLists expenses (project-linked spend such as travel, purchases, or pass-through costs). Supports project, client, vendor, expense category, invoiced, date, and cursor filters.
list_invoices
ChatGPTLists invoices (client billing documents sent or ready to send). Use get_invoice for line items, source records, and PDF details. Use list_projects and list_clients to resolve IDs. Supports project, client, company, status, type, date, due-date, sent/ready filters, and cursor pagination.
list_people
ChatGPTLists people (employees and contractors) with current availability, employment from and through dates (null when employment has no start or end), the current site, and the dated site assignment series. Use person for exact name/ID match or person="me" for the current user; use search (min 3 chars) for substring name search. Use get_person for assignment IDs and manage_person siteAssignments to change the series. Supports filtering by site, role, group, company, or availability.
list_positions
ChatGPTLists positions (person-to-project assignments). A position connects a person to a project with a role. Use assignedPerson with person ID, name, or "me" for the current user. Use get_position for full details including allocations. Use manage_positions to create, update, archive, or restore positions. Supports filtering by project, person, role, site, or the position's own group.
list_projects
ChatGPTLists projects (client engagements or internal initiatives). Use list_positions to see people assigned to a project. Supports filtering by client, owner, status, site, or tags.
list_reference_data
ChatGPTLists selected reference data (tenant taxonomies and safe defaults) for project, staffing, reporting, and finance workflows. Use it before manage_project, manage_person, manage_positions, manage_allocations, reports, or filtered list tools to find stable IDs. Supports groups plus per-group filters and pagination.
list_tenants
ChatGPTLists MCP-enabled tenant memberships for the authenticated user. Use this before tenant-scoped tools to pick a tenantId.
list_time_entries
ChatGPTLists time entries (logged hours against projects and tasks). Use person="me" to get your own entries. Supports filtering by project, client, task, person, and entry date range (from/through as YYYY-MM-DD).
manage_allocations
ChatGPTCreates, updates, moves, or removes allocations (planned work blocks on positions). Use list_allocations or get_position for allocation IDs, list_positions for position IDs. Status and task IDs come from list_reference_data. Allocation capacity uses percentage in 10 000ths (1 000 000 = 100%), not capacityPercentage. Returns per-item results so failed staffing changes can be retried.
manage_budget_progress
ChatGPTCreates, updates, or removes a budget's progress entries (how much of a fixed-price budget is complete by a date; drives revenue recognition). progressAmount is cumulative money from the budget's start as { amount, currency } in the budget's currency, not a percent. Example: items: [{ date, progressAmount }] creates, [{ id, note }] updates only the note, remove: [entryId]. An entry below the one before it is a reduction and needs a note; only the latest entry may be one. Budget and entry IDs come from get_project. All changes apply together or not at all. Entries with a milestoneId change only through their milestone.
manage_client
ChatGPTCreates or updates one client (a company you work for). Use list_clients to find client IDs and list_people for owner IDs. Client tag IDs come from list_reference_data. Returns the affected client summary.
manage_person
ChatGPTCreates or updates one person (employee or contractor) for staffing and reporting. Use list_people/get_person for person IDs. Dated site periods use siteAssignments and company periods use companyAssignments (row IDs from get_person); flat siteId is create-only. Role, skill, group, and company IDs come from list_reference_data. Returns assignment IDs for follow-up.
manage_positions
ChatGPTCreates, updates, archives, or restores positions (person-to-project assignments). Use list_projects, list_people, and get_project. Role, seniority, and site IDs come from list_reference_data. Position fields use competenceRoleId and competenceRoleSeniorityId (not roleId). Use manage_allocations separately for planned work blocks.
manage_project
ChatGPTCreates or updates one project (client engagement or internal initiative) and its project-level setup. Use list_projects/get_project for project IDs and list_clients for clientId. Company, site, status, tag, and group IDs come from list_reference_data. Task IDs for assigning tasks come from list_reference_data (tasks). Set archived true/false on an existing project to archive or unarchive; archived true cannot be combined with other fields. Changing to a status in another category recalculates the project's figures and can end its plan, change allocation statuses, unarchive the project, or be refused; see statusId. Use manage_positions for staffing, manage_project_financial_plan for budgets, planned expenses, and rate card assignments, phases.items (with name) to add phases visible on get_project, phases.items billingType to give a phase its own pricing, and notes.add, notes.update, and notes.remove for project notes. Note IDs come from get_project. notes.add takes noteText and noteDate.
manage_project_expenses
ChatGPTCreates, updates, or removes actual expenses (project-linked spend such as travel, purchases, or pass-through costs). Payload shape: expenses.items[] with top-level name and currency per expense. Line items use expenseRate and amountToInvoice as { amount, currency }, plus quantity, description, billedFromClient, and categoryId. Markup is not a separate field; set the client billable amount with amountToInvoice. Omit lineItems to leave lines unchanged. If every line in lineItems has an id, only those lines are patched and the others stay, for example lineItems: [{ id, amountToInvoice: { amount, currency } }]. If any line has no id, lineItems replaces the set: lines with an id are updated, lines without an id are created, and omitted existing lines are deleted. An invoiced expense cannot be removed through expenses.remove; handle it in Operating. Use get_project/list_expenses to inspect existing IDs. Category and vendor IDs come from list_reference_data. Use manage_project_financial_plan for budgets and planned expenses.
manage_project_financial_plan
ChatGPTCreates, updates, or removes project planned financial records: budgets, budget schedules, expense budgets, planned expenses, and rate card assignments. Set the project currency via manage_project before creating budget, budget schedule, or planned expense lines. Example: budgets.items: [{ name, from, through, amount: { amount, currency } }]; plannedExpenses.items: [{ description, date, currency, cost }]; use budgets.remove or plannedExpenses.remove for deletions without dummy items. A budget schedule repeats one budget per period and is how a retainer is set up; a retainer project or phase uses budgetSchedules instead of budgets. A phase with its own billing type (get_project.phases) has its own budgets: pass its phaseId when creating a budget or budget schedule for it. Use get_project to inspect current IDs. Category, vendor, and rate card IDs come from list_reference_data. Use manage_project_expenses for actual tracked expenses and manage_project for project configuration.
move_allocations
ChatGPTMoves one or more allocations (scheduled time blocks) to a different target position. Allocations keep their dates, percentages, and other properties — only the parent position changes. This might affect rates or total effort if the position has different attributes.Requires allocation IDs from get_position or list_allocations, and a target positionId from list_positions. Prefer manage_allocations for planned-work move workflows and mixed batches.
move_positions
ChatGPTMoves one or more positions (person-to-project assignments) to a different target project. Positions keep their allocations, assigned person, and other properties — only the parent project changes. This might affect financials if e.g. the projects have different rates or billing types.Requires position IDs from list_positions and a target projectId from list_projects. Prefer manage_positions for position workflow changes.
report_actual
ChatGPTReports actual work and earned revenue over a date range. Use dateRange.startDate and dateRange.endDate (YYYY-MM-DD), not top-level from/through. Always paginated by person/project: pass limit (default 50) and use meta.nextCursor as cursor for the next page. include.projectBreakdown requires groupBy person. Supports project/person grouping, week/month/total buckets, optional breakdowns, non-person revenue, and opt-in costs.
report_planned
ChatGPTReports planned work, revenue, tentative work, and utilization over a date range. Use dateRange.startDate and dateRange.endDate (YYYY-MM-DD), not top-level from/through. Requires dateRange, groupBy, and bucketBy (week | month | total). Always paginated by person/project: pass limit (default 50) and use meta.nextCursor as cursor for the next page. include.utilization and include.availability require groupBy person. Supports project/person grouping, week/month/total buckets, optional breakdowns, and opt-in costs.
start_timer
ChatGPTStarts your timer (a running stopwatch). date (YYYY-MM-DD) is the day the time entry lands on; send your local today. Refuses when one is already running and leaves it running. projectId is from list_projects; taskId and positionId from get_project; siteId from list_reference_data. Stop it with stop_timer. track_time writes a finished duration instead.
stop_timer
ChatGPTStops your running timer and returns the time entry it wrote. Omit timeEntryId to create an entry. Send an ID from list_time_entries to add the elapsed time onto that matching entry, when it is not submitted, approved, or invoiced. timeEntry is null when less than one second elapsed. Read the timer with get_timer first.
submit_timesheet
ChatGPTSubmits every unsubmitted time entry for a person on or before the given date, and sets that date as their submitted-through date. The date is inclusive. An earlier date moves the marker and leaves later entries submitted. A missing required note fails the call and submits nothing. person is a positive integer ID or "me", not a name. Use list_people or get_person to find another person.
track_time
ChatGPTCreates a time entry (logged hours against a project). Use person="me" to create entries for yourself. Requires projectId from list_projects or get_project, date (YYYY-MM-DD), and seconds. When the project has assigned tasks, taskId from get_project is required. When the person has more than one position on the project, positionId from get_project is required; each position belongs to a phase. Taxonomy IDs come from list_reference_data. Returns the created entry; use list_time_entries to see it in context.