Skip to main content
Glama

getTasksMetricsComplete

Retrieve the total count of completed tasks in Teamwork to monitor project progress and completion metrics.

Instructions

Get the total count of completed tasks in Teamwork

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the getTasksMetricsComplete tool logic. It calls the Teamwork API endpoint /tasks/metrics/complete.json and returns the response data.
    export async function handleGetTasksMetricsComplete() {
      try {
        logger.info('Getting metrics for completed tasks');
        
        // Make API call
        const apiClient = getApiClientForVersion();
        const response = await apiClient.get('/tasks/metrics/complete.json');
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }]
        };
      } catch (error: any) {
        return createErrorResponse(error, 'Retrieving completed tasks metrics');
      }
    } 
  • The tool definition/schema for getTasksMetricsComplete. Defines the tool name, description, input schema (no params needed), and annotations.
    export const getTasksMetricsCompleteDefinition = {
      name: "getTasksMetricsComplete",
      description: "Get the total count of completed tasks in Teamwork",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      },
      annotations: {
        title: "Get the Total Count of Completed Tasks",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false
      }
    };
  • Import of the getTasksMetricsComplete definition and handler from its source file.
    import { getTasksMetricsCompleteDefinition as getTasksMetricsComplete, handleGetTasksMetricsComplete } from './tasks/getTasksMetricsComplete.js';
  • Registration of the tool pair (definition + handler) in the toolPairs array.
    { definition: getTasksMetricsComplete, handler: handleGetTasksMetricsComplete },
  • Re-export of handleGetTasksMetricsComplete from the tools index.
    export { handleGetTasksMetricsComplete } from './tasks/getTasksMetricsComplete.js';
  • Listing of 'getTasksMetricsComplete' in the 'Tasks' tool group within the configuration.
    'Tasks': ['getTasks', 'getTasksByProjectId', 'getTaskListsByProjectId', 'getTaskById', 'createTask', 'createSubTask', 'updateTask', 'deleteTask', 'getTasksMetricsComplete', 'getTasksMetricsLate', 'getTaskSubtasks', 'getTaskComments'],
Behavior1/5

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

Description implies a read-only operation ('Get'), but annotations set readOnlyHint to false, creating a contradiction. No additional behavioral context beyond annotations.

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?

Single, concise sentence with no redundant information. Appropriate length for a simple tool.

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

Completeness4/5

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

For a tool with no parameters and no output schema, the description sufficiently conveys its purpose. However, it could mention the return format (e.g., integer) for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. Description adds no parameter-specific info, but baseline 4 applies per rules.

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?

Description clearly states the action (Get) and resource (total count of completed tasks). It differentiates from siblings like getTasksMetricsLate but could be more explicit about its distinction from getTasks or other metric tools.

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 (e.g., getTasksMetricsLate). No explicit when-not or alternative tools mentioned.

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