Skip to main content
Glama

getProjectsPeopleMetricsPerformance

Analyze team performance by tracking completed tasks per user during specified periods to identify top contributors and productivity trends.

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

  • The main MCP tool handler function. It calls the getPeopleMetricsPerformance service with input parameters and returns the response as formatted JSON or an error response.
    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');
      }
    } 
  • The tool schema/definition including name, description, input schema for parameters (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
      }
    };
  • Registration of the tool's definition and handler in the central toolPairs array, which populates toolDefinitions and toolHandlersMap for MCP.
    { definition: getProjectsPeopleMetricsPerformance, handler: handleGetProjectsPeopleMetricsPerformance },
  • Helper service function that performs the actual API call to Teamwork's /people/metrics/performance.json endpoint with the provided parameters.
    export async function getPeopleMetricsPerformance(params: GetPeopleMetricsPerformanceParams = {}) {
      const api = getApiClientForVersion('v3');
      const response = await api.get('/people/metrics/performance.json', { params });
      return response.data;
    }
    
    export default getPeopleMetricsPerformance; 
  • Import of the tool definition and handler from the implementation file.
    import { getProjectsPeopleMetricsPerformanceDefinition as getProjectsPeopleMetricsPerformance, handleGetProjectsPeopleMetricsPerformance } from './people/getPeopleMetricsPerformance.js';
Behavior3/5

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

Annotations indicate readOnlyHint=false, openWorldHint=false, and destructiveHint=false, suggesting it's a non-destructive read operation with limited scope. The description adds context about default sorting order and period-based filtering, which is useful beyond annotations. However, it doesn't disclose behavioral traits like rate limits, authentication needs, or output format details, leaving gaps in understanding.

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 concise and front-loaded, with two sentences that efficiently convey core functionality and default behavior. Every sentence adds value, though it could be slightly more structured (e.g., separating purpose from behavioral notes). No wasted words or 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?

Given the tool's complexity (performance metrics with three parameters), lack of output schema, and annotations covering basic safety, the description is moderately complete. It explains what the tool does but lacks details on output format, error handling, or prerequisites. This leaves the agent with incomplete context for effective use.

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%, with clear descriptions for startDate, endDate, and orderMode (including enum values). The description adds minimal semantic value beyond the schema, only implying period-based filtering without specifying date formats or clarifying parameter interactions. Baseline 3 is appropriate as the schema adequately documents parameters.

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's purpose: 'Count the number of completed tasks by user for the provided period' and 'Performance of users completing the most tasks.' This specifies the verb (count), resource (completed tasks by user), and scope (provided period). However, it doesn't explicitly differentiate from sibling tools like 'getProjectsReportingUserTaskCompletion' or 'getTasksMetricsComplete,' which may have overlapping functionality.

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. It mentions default sorting behavior ('By default the user with the most completed tasks is shown first'), but offers no explicit when/when-not rules or references to sibling tools. This leaves the agent without clear context for selection among similar metrics or reporting tools.

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