Skip to main content
Glama

getProjectsPeopleMetricsPerformance

Count completed tasks per user within a specified date range and order results by task completion count to identify top performers.

Instructions

Performance of users completing the most tasks. Count the number of completed tasks by user for the provided period. By default the user with the most completed tasks is shown first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateNoStart date for the performance metrics period
endDateNoEnd date for the performance metrics period
orderModeNoOrder mode for sorting results

Implementation Reference

  • Handler function that calls the service and returns the response as text content.
    export async function handleGetProjectsPeopleMetricsPerformance(input: any) {
      try {
        const response = await getPeopleMetricsPerformance(input);
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response, null, 2)
          }]
        };
      } catch (error: any) {
        return createErrorResponse(error, 'Retrieving people performance metrics');
      }
    } 
  • Tool definition with input schema (startDate, endDate, orderMode) and annotations.
    export const getProjectsPeopleMetricsPerformanceDefinition = {
      name: "getProjectsPeopleMetricsPerformance",
      description: "Performance of users completing the most tasks. Count the number of completed tasks by user for the provided period. By default the user with the most completed tasks is shown first.",
      inputSchema: {
        type: 'object',
        properties: {
          startDate: {
            type: 'string',
            description: 'Start date for the performance metrics period'
          },
          endDate: {
            type: 'string',
            description: 'End date for the performance metrics period'
          },
          orderMode: {
            type: 'string',
            description: 'Order mode for sorting results',
            enum: [
              'asc',
              'desc'
            ]
          }
        }
      },
      annotations: {
        title: "Get the Metrics of People's Performance in Projects",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false
      }
    };
  • Tool registered in the toolPairs array with its definition and handler.
    { definition: getProjectsPeopleMetricsPerformance, handler: handleGetProjectsPeopleMetricsPerformance },
  • Import of the definition and handler in the tools index.
    import { getProjectsPeopleMetricsPerformanceDefinition as getProjectsPeopleMetricsPerformance, handleGetProjectsPeopleMetricsPerformance } from './people/getPeopleMetricsPerformance.js';
  • Re-export of the handler from the tools index.
    export { handleGetProjectsPeopleMetricsPerformance } from './people/getPeopleMetricsPerformance.js';
  • Service layer function that makes the actual API call to /people/metrics/performance.json.
    import { getApiClientForVersion } from '../core/apiClient.js';
    
    interface GetPeopleMetricsPerformanceParams {
      startDate?: string;
      endDate?: string;
      orderMode?: 'asc' | 'desc';
    }
    
    export async function getPeopleMetricsPerformance(params: GetPeopleMetricsPerformanceParams = {}) {
      const api = getApiClientForVersion('v3');
      const response = await api.get('/people/metrics/performance.json', { params });
      return response.data;
    }
Behavior3/5

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

The description describes a read-like operation (counting/showing), but annotations have readOnlyHint=false, which is neutral—not a contradiction. The description does not disclose additional behaviors such as authentication requirements or side effects, but given the simple counting nature, this is acceptable.

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?

The description is extremely concise with two sentences, front-loading the main purpose. Every sentence adds value without redundancy.

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 tool with no output schema, the description lacks detail on the return format (e.g., list of users with counts). It is adequate for a simple tool but could be improved by specifying the output structure.

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%, so parameters are well-documented. The description adds minor value by stating the default sort order (most completed tasks first), which relates to the 'orderMode' parameter but does not explicitly tie it. This provides slight additional context.

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 shows performance of users by counting completed tasks for a period, which is specific and actionable. However, it does not differentiate from the similarly named sibling tool 'getProjectsReportingUserTaskCompletion', leaving ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for viewing task completion performance and notes default ordering, but does not specify when to use this tool over alternatives like 'getProjectsPeopleUtilization' or 'getTasksMetricsComplete'. No explicit when-not or alternative suggestions.

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