Skip to main content
Glama

getTasksMetricsLate

Retrieve the total count of late tasks in Teamwork to identify overdue work and manage project timelines.

Instructions

Get the total count of late tasks in Teamwork

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic. Calls the Teamwork API endpoint /tasks/metrics/late.json and returns the count of late tasks.
    export async function handleGetTasksMetricsLate() {
      try {
        logger.info('Getting metrics for late tasks');
        
        // Make API call
        const apiClient = getApiClientForVersion();
        const response = await apiClient.get('/tasks/metrics/late.json');
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(response.data, null, 2)
          }]
        };
      } catch (error: any) {
        return createErrorResponse(error, 'Retrieving late tasks metrics');
      }
    } 
  • The tool definition/schema for getTasksMetricsLate. Defines the tool name, description, empty input schema (no parameters required), and annotations.
    export const getTasksMetricsLateDefinition = {
      name: "getTasksMetricsLate",
      description: "Get the total count of late tasks in Teamwork",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      },
      annotations: {
        title: "Get the Total Count of Late Tasks",
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: false
      }
    };
  • Re-export of the handler from the tools index file.
    export { handleGetTasksMetricsLate } from './tasks/getTasksMetricsLate.js';
  • Registration of the tool pair (definition + handler) in the toolPairs array for the MCP server.
    { definition: getTasksMetricsLate, handler: handleGetTasksMetricsLate },
  • Configuration grouping: 'getTasksMetricsLate' is listed under the 'Tasks' group in the toolGroups mapping.
    '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?

The description claims to 'Get' data, implying a read-only operation, but the readOnlyHint annotation is false, indicating potential mutation. This is a direct contradiction. The description also fails to disclose any behavioral traits like authentication requirements or how 'late' is defined.

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 sentence without excess words. It is concise, but could be slightly more structured to include key details like the definition of 'late'.

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 simple count tool with no parameters and no output schema, the description is minimally adequate. However, it lacks context on what constitutes a late task and the expected output format, leaving some ambiguity.

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?

The input schema has no parameters, so schema coverage is 100%. The description does not need to add parameter semantics since none exist. Baseline score of 4 applies.

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 retrieves the total count of late tasks. It uses a specific verb ('Get') and resource ('total count of late tasks'). However, it does not explicitly differentiate from similar sibling tools like getTasksMetricsComplete, which likely retrieves counts of completed tasks.

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 is provided on when to use this tool versus alternatives such as getTasksMetricsComplete or getTasks. There is no mention of context, prerequisites, or when not to use it.

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