Skip to main content
Glama

getProjectsPeopleUtilization

Retrieve user utilization data to analyze billable and non-billable time, availability, and key metrics for project resource management.

Instructions

Return the user utilization data. This endpoint provides detailed information about user utilization, including billable and non-billable time, availability, and various utilization metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoomNodetermine the type of zoom filter used to display on the report
startDateNofilter by start date
sortOrderNoorder mode
sortNosort by (deprecated, use orderBy)
searchTermNofilter by user first or last name
reportFormatNodefine the format of the report
orderModeNogroup by
orderByNosort by
groupByNogroup by
endDateNofilter by end date
pageSizeNonumber of items in a page
pageNopage number
skipCountsNoskip doing counts on a list API endpoint for performance reasons
legacyResponseNoreturn response without summary and its legacy body structure
isReportDownloadNogenerate a report document
isCustomDateRangeNodetermine if the query is for a custom date range
includeUtilizationsNoadds report rows for individual entities
includeTotalsNoadds report summary to response
includeCollaboratorsNoinclude collaborators
includeClientsNoinclude client users
includeArchivedProjectsNoinclude archived projects
IncludeCompletedTasksNoinclude completed tasks
userIdsNofilter by userIds
teamIdsNofilter by team ids
selectedColumnsNocustomise the report by selecting columns to be displayed
projectIdsNofilter by project ids
jobRoleIdsNofilter by jobrole ids
includeNoinclude additional data
fieldsUtilizationsNoQuery parameter: fields[utilizations] - specific utilization fields to include
fieldsUsersNoQuery parameter: fields[users] - specific user fields to include
companyIdsNofilter by company ids

Implementation Reference

  • The handler function handleGetProjectsPeopleUtilization that executes the tool logic. Maps camelCase fields to API format, calls getPeopleUtilization service, and returns JSON response or error.
    export async function handleGetProjectsPeopleUtilization(input: any) {
      // Map camelCase field names back to API format
      const apiInput: Record<string, any> = { ...input };
    
      // Define the mapping for fields[...] parameters
      const fieldMappings: Record<string, string> = {
        fieldsUtilizations: "fields[utilizations]",
        fieldsUsers: "fields[users]",
      };
    
      for (const [camelCaseKey, apiKey] of Object.entries(fieldMappings)) {
        if (apiInput[camelCaseKey] !== undefined) {
          apiInput[apiKey] = apiInput[camelCaseKey];
          delete apiInput[camelCaseKey];
        }
      }
    
      try {
        const response = await getPeopleUtilization(apiInput);
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response, null, 2)
          }]
        };
      } catch (error: any) {
        return createErrorResponse(error, 'Getting people utilization');
      }
    } 
  • The tool definition (getProjectsPeopleUtilizationDefinition) including input schema with all parameters (zoom, startDate, sortOrder, sort, searchTerm, reportFormat, orderMode, orderBy, groupBy, endDate, pageSize, page, userIds, projectIds, teamIds, etc.) and annotations.
    export const getProjectsPeopleUtilizationDefinition = {
      name: "getProjectsPeopleUtilization",
      description: "Return the user utilization data. This endpoint provides detailed information about user utilization, including billable and non-billable time, availability, and various utilization metrics.",
      inputSchema: {
        type: 'object',
        properties: {
          zoom: {
            type: 'string',
            description: 'determine the type of zoom filter used to display on the report',
            enum: [
              'week',
              'month',
              'last3months',
              'quarterbyweek',
              'quarterbymonth'
            ]
          },
          startDate: {
            type: 'string',
            description: 'filter by start date'
          },
          sortOrder: {
            type: 'string',
            description: 'order mode',
            enum: [
              'asc',
              'desc'
            ]
          },
          sort: {
            type: 'string',
            description: 'sort by (deprecated, use orderBy)',
            enum: [
              'name',
              'percentutilization',
              'percentestimatedutilization',
              'availableminutes',
              'unavailableminutes',
              'loggedminutes',
              'billableminutes',
              'unbillableminutes',
              'billableutilization',
              'nonbillableutilization'
            ]
          },
          searchTerm: {
            type: 'string',
            description: 'filter by user first or last name'
          },
          reportFormat: {
            type: 'string',
            description: 'define the format of the report',
            enum: [
              'pdf'
            ]
          },
          orderMode: {
            type: 'string',
            description: 'group by',
            enum: [
              'weekly',
              'monthly'
            ]
          },
          orderBy: {
            type: 'string',
            description: 'sort by',
            enum: [
              'name',
              'percentutilization',
              'percentestimatedutilization',
              'availableminutes',
              'unavailableminutes',
              'loggedminutes',
              'billableminutes',
              'unbillableminutes',
              'companycount',
              'achieved',
              'target',
              'allocatedutilization',
              'totalworkingminutes',
              'availableutilization',
              'unavailableutilization'
            ]
          },
          groupBy: {
            type: 'string',
            description: 'group by',
            enum: [
              'day',
              'week',
              'month'
            ]
          },
          endDate: {
            type: 'string',
            description: 'filter by end date'
          },
          pageSize: {
            type: 'integer',
            description: 'number of items in a page'
          },
          page: {
            type: 'integer',
            description: 'page number'
          },
          skipCounts: {
            type: 'boolean',
            description: 'skip doing counts on a list API endpoint for performance reasons'
          },
          legacyResponse: {
            type: 'boolean',
            description: 'return response without summary and its legacy body structure'
          },
          isReportDownload: {
            type: 'boolean',
            description: 'generate a report document'
          },
          isCustomDateRange: {
            type: 'boolean',
            description: 'determine if the query is for a custom date range'
          },
          includeUtilizations: {
            type: 'boolean',
            description: 'adds report rows for individual entities'
          },
          includeTotals: {
            type: 'boolean',
            description: 'adds report summary to response'
          },
          includeCollaborators: {
            type: 'boolean',
            description: 'include collaborators'
          },
          includeClients: {
            type: 'boolean',
            description: 'include client users'
          },
          includeArchivedProjects: {
            type: 'boolean',
            description: 'include archived projects'
          },
          IncludeCompletedTasks: {
            type: 'boolean',
            description: 'include completed tasks'
          },
          userIds: {
            type: 'array',
            items: {
              type: 'integer'
            },
            description: 'filter by userIds'
          },
          teamIds: {
            type: 'array',
            items: {
              type: 'integer'
            },
            description: 'filter by team ids'
          },
          selectedColumns: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'customise the report by selecting columns to be displayed'
          },
          projectIds: {
            type: 'array',
            items: {
              type: 'integer'
            },
            description: 'filter by project ids'
          },
          jobRoleIds: {
            type: 'array',
            items: {
              type: 'integer'
            },
            description: 'filter by jobrole ids'
          },
          include: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'include additional data'
          },
          fieldsUtilizations: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'Query parameter: fields[utilizations] - specific utilization fields to include'
          },
          fieldsUsers: {
            type: 'array',
            items: {
              type: 'string'
            },
            description: 'Query parameter: fields[users] - specific user fields to include'
          },
          companyIds: {
            type: 'array',
            items: {
              type: 'integer'
            },
            description: 'filter by company ids'
          }
        }
      },
      annotations: {
        title: "Get the Utilization of People in Projects",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false
      }
    };
  • Import of getProjectsPeopleUtilizationDefinition (aliased as getProjectsPeopleUtilization) and handleGetProjectsPeopleUtilization from the people/getPeopleUtilization.ts module.
    import { getProjectsPeopleUtilizationDefinition as getProjectsPeopleUtilization, handleGetProjectsPeopleUtilization } from './people/getPeopleUtilization.js';
  • Registration of the tool in the toolPairs array, pairing the definition with its handler for export.
    { definition: getProjectsPeopleUtilization, handler: handleGetProjectsPeopleUtilization },
  • The service function getPeopleUtilization that makes the actual API call to GET /people/utilization.json using the v3 API client.
    export async function getPeopleUtilization(params: GetPeopleUtilizationParams = {}) {
      const api = getApiClientForVersion('v3');
      const response = await api.get('/people/utilization.json', { params });
      return response.data;
    }
Behavior2/5

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

The description only states it returns data, but annotations indicate readOnlyHint=false, which could be contradictory. No details on pagination, rate limits, or side effects. The description adds minimal behavioral context beyond what annotations provide.

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?

Two concise sentences with no fluff. Front-loaded with the core action and immediately specifies what data is included.

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?

Despite 31 parameters and no output schema, the description is only two sentences. It lacks explanation of how parameters affect results, return structure, or behavior. For a complex reporting tool, this is insufficient.

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?

All 31 parameters have descriptions in the schema (100% coverage). The tool description summarizes output fields but does not add extra meaning to parameters. Baseline 3 is appropriate.

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 the tool returns user utilization data, including billable and non-billable time, availability, and metrics. The verb 'Return' and resource 'user utilization data' are specific. However, it does not differentiate from sibling tools like getProjectsReportingUtilization, which may have overlapping purpose.

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 or when to avoid it. The description lacks any usage context, prerequisites, or exclusions.

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/Vizioz/Teamwork-MCP'

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