Skip to main content
Glama

getTasksMetricsLate

Counts late tasks in Teamwork projects to monitor project delays and track overdue work for timely completion.

Instructions

Get the total count of late tasks in Teamwork

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the getTasksMetricsLate tool. It fetches late tasks metrics from the Teamwork API endpoint '/tasks/metrics/late.json', formats the response as JSON text, and handles any errors using createErrorResponse.
    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 schema/definition, specifying the name, description, empty input schema (no parameters required), and annotations for UI hints.
    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
      }
    };
  • Registration of the tool in the central toolPairs array, linking the definition and handler for inclusion in toolDefinitions and toolHandlersMap.
    { definition: getTasksMetricsLate, handler: handleGetTasksMetricsLate },
  • Import of the tool definition and handler from the specific implementation file.
    import { getTasksMetricsLateDefinition as getTasksMetricsLate, handleGetTasksMetricsLate } from './tasks/getTasksMetricsLate.js';
  • Re-export of the handler for use elsewhere in the codebase.
    export { handleGetTasksMetricsLate } from './tasks/getTasksMetricsLate.js';
Behavior3/5

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

Annotations indicate this is a non-destructive, non-read-only operation with no open-world hint, but the description doesn't add behavioral context beyond that. It doesn't specify if this requires authentication, has rate limits, or what the return format might be, though annotations cover basic safety. No contradiction with annotations is present.

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 a single, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficiently conveys the essential information in a compact form.

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 has no parameters, no output schema, and annotations provide basic behavioral hints, the description is minimally adequate. However, it lacks details on what 'late tasks' means, timeframes, or how the count is calculated, which could be useful for an agent in a more complex context.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the lack of inputs. The description doesn't need to add parameter details, so it meets the baseline for this scenario without compensation needed.

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 verb 'Get' and the resource 'total count of late tasks in Teamwork', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'getTasksMetricsComplete', which might have similar naming patterns but different metrics.

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 doesn't mention any prerequisites, context, or exclusions, leaving the agent to infer usage based on the name alone without explicit direction.

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