Skip to main content
Glama

getProjectsReportingUtilization

Generate utilization reports for projects in CSV, HTML, PDF, or XLSX formats. Filter by date, users, teams, or projects to analyze resource allocation and track logged time.

Instructions

Generate utilization report in various formats (CSV, HTML, PDF, XLSX). Generates a utilization report containing all people for the provided filters. Only the people that the logged-in user can access will be returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatYesThe format of the report
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
skipCountsNoSkipCounts allows you to skip 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
fieldsUtilizationsNoQuery parameter: fields[utilizations]
fieldsUsersNoQuery parameter: fields[users]
companyIdsNofilter by company ids

Implementation Reference

  • The MCP tool handler function for 'getProjectsReportingUtilization'. It calls the utilization service with input parameters and returns the data as JSON text or error response.
    export async function handleGetProjectsReportingUtilization(input: any) {
      try {
        const data = await getUtilization({ ...input, format: input.format.toLowerCase() });
        return {
          content: [{
            type: "text",
            text: JSON.stringify(data, null, 2)
          }]
        };
      } catch (error: any) {
        return createErrorResponse(error, 'Getting utilization report');
      }
    } 
  • The tool definition including name, description, input schema with numerous filter parameters (format, dates, sorts, includes, etc.), and annotations.
    export const getProjectsReportingUtilizationDefinition = {
      name: "getProjectsReportingUtilization",
      description: "Generate utilization report in various formats (CSV, HTML, PDF, XLSX). Generates a utilization report containing all people for the provided filters. Only the people that the logged-in user can access will be returned.",
      inputSchema: {
        type: 'object',
        properties: {
          format: {
            type: 'string',
            description: 'The format of the report',
            enum: ['csv', 'html', 'pdf', 'xlsx']
          },
          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: 'SkipCounts allows you to 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',
            description: 'filter by userIds'
          },
          teamIds: {
            type: 'array',
            description: 'filter by team ids'
          },
          selectedColumns: {
            type: 'array',
            description: 'customise the report by selecting columns to be displayed.'
          },
          projectIds: {
            type: 'array',
            description: 'filter by project ids'
          },
          jobRoleIds: {
            type: 'array',
            description: 'filter by jobrole ids'
          },
          include: {
            type: 'array',
            description: 'include'
          },
          fieldsUtilizations: {
            type: 'array',
            description: 'Query parameter: fields[utilizations]'
          },
          fieldsUsers: {
            type: 'array',
            description: 'Query parameter: fields[users]'
          },
          companyIds: {
            type: 'array',
            description: 'filter by company ids'
          }
        },
        required: ['format']
      },
      annotations: {
        title: "Get the Utilization of People in Projects",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false
      }
    };
  • Registration of the tool in the toolPairs array, pairing the definition and handler for inclusion in toolDefinitions and toolHandlersMap.
    { definition: getProjectsReportingUtilization, handler: handleGetProjectsReportingUtilization },
  • Re-export of the handler from the implementation file for use in the tools index.
    export { handleGetProjectsReportingUtilization } from './people/getUtilization.js';
  • Supporting service function called by the tool handler. Makes an API call to the backend endpoint for utilization report.
    async function getUtilization(params: GetUtilizationParams) {
      const api = ensureApiClient();
      const endpoint = `/reporting/precanned/utilization.${params.format}`;
      const response = await api.get(endpoint, { params });
      return response.data;
    }
Behavior3/5

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

Annotations already indicate this is non-destructive and non-readOnly, which the description's 'generate' action aligns with. The description adds useful context about access restrictions (only accessible people returned) and output formats, but doesn't mention performance implications, rate limits, or what happens with the 32 parameters when unspecified.

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?

The description is reasonably concise (two sentences) but could be better structured. The first sentence redundantly mentions 'generate' twice, and the second sentence adds important access context but could be integrated more smoothly. It's front-loaded with the core purpose.

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?

For a complex 32-parameter reporting tool with no output schema, the description is adequate but minimal. It covers the core purpose and access restrictions, but doesn't explain the report's structure, content beyond 'people', or how parameters interact. Given the complexity, more guidance would be helpful despite good schema coverage.

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?

With 100% schema description coverage, the schema comprehensively documents all 32 parameters. The description only mentions 'filters' generically and output formats, adding minimal semantic value beyond what's already in the structured schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 generates a utilization report in various formats containing people data based on filters, with specific mention of access restrictions. It distinguishes from siblings by focusing on reporting rather than CRUD operations, though it doesn't explicitly differentiate from similar reporting tools like 'getProjectsPeopleUtilization'.

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 minimal usage guidance - only mentioning that it returns people accessible to the logged-in user. It doesn't explain when to use this vs. other reporting tools (like 'getProjectsPeopleUtilization'), what scenarios warrant its use, or any prerequisites beyond authentication.

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