Skip to main content
Glama

getProjectsPeopleUtilization

Analyze team utilization metrics across projects to track billable time, availability, and resource allocation for informed workforce management decisions.

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 MCP tool handler that adapts input parameters (mapping camelCase to API fields), invokes the getPeopleUtilization service, and returns the JSON response as text content or an error response.
    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's input schema definition, including detailed properties for filters, sorting, pagination, and report options matching the API parameters.
    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
      }
    };
  • Registration of the tool by pairing its definition and handler in the toolPairs array, which is used to generate toolDefinitions array and toolHandlersMap for MCP tool exposure.
    { definition: getProjectsPeopleUtilization, handler: handleGetProjectsPeopleUtilization },
  • Supporting service utility that performs the actual API request to retrieve people utilization data 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;
    }
Behavior3/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=false, covering basic safety and scope. The description adds value by specifying the type of data returned (e.g., 'detailed information about user utilization'), but does not disclose additional behavioral traits like rate limits, authentication needs, or performance implications 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Return the user utilization data') and adds relevant details without waste. It is appropriately sized for the tool's complexity, though it could be slightly more structured to highlight key features.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high parameter count (31) and lack of output schema, the description is minimally adequate. It clarifies the data type returned but does not address output format, pagination, or error handling. With annotations covering basic traits, it provides a foundation but leaves gaps for a complex reporting tool.

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 31 parameters. The description adds no parameter-specific semantics beyond implying a focus on 'user utilization data', which aligns with the schema but does not provide additional context or examples. This meets the baseline for high schema coverage.

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 states the tool 'Return[s] the user utilization data' and lists specific metrics like 'billable and non-billable time, availability, and various utilization metrics', which clarifies the resource and scope. However, it does not explicitly differentiate from sibling tools like 'getProjectsPeopleMetricsPerformance' or 'getProjectsReportingUtilization', making the purpose somewhat vague in context.

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 tool versus alternatives, such as sibling tools like 'getProjectsPeopleMetricsPerformance' or 'getProjectsReportingUtilization'. It lacks explicit context, prerequisites, or exclusions, offering only a general statement about what data is returned without usage instructions.

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