Skip to main content
Glama

getTask

Retrieve specific tasks from the Godspeed task application by providing a task ID using the API-enabled MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • src/index.ts:68-85 (registration)
    Registration of the MCP 'getTask' tool, including input schema and thin wrapper handler that delegates to GodspeedAPI.getTask and formats the response.
    server.tool(
        "getTask",
        {
            id: z.string()
        },
        async ({ id }) => {
            try {
                const result = await godspeedApi.getTask(id);
                return {
                    content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
                };
            } catch (error) {
                return {
                    content: [{ type: "text", text: `Error: ${error instanceof Error ? error.message : String(error)}` }]
                };
            }
        }
    );
  • Core handler logic for retrieving a task by ID via HTTP GET to the Godspeed API endpoint /tasks/{id}, with authentication and error handling.
    async getTask(id: string): Promise<ApiResponse<Task>> {
        try {
            if (!id) {
                throw new Error('Task ID is required');
            }
    
            const headers = this.getAuthHeaders();
    
            const response = await fetch(`${API_BASE_URL}/tasks/${id}`, {
                method: 'GET',
                headers,
            });
    
            const data = await response.json();
    
            if (!response.ok) {
                throw new Error(data.error || 'Failed to get task');
            }
    
            return data;
        } catch (error) {
            throw new Error(`Get task error: ${error instanceof Error ? error.message : String(error)}`);
        }
    }
  • Zod input schema for the 'getTask' tool, requiring a string 'id' parameter.
    {
        id: z.string()
    },
  • TypeScript interface defining the Task object returned by the getTask tool.
    export interface Task {
        id?: string;
        title: string;
        list_id: string;
        location?: string;
        notes?: string;
        due_at?: Date;
        timeless_due_at?: string;
        starts_at?: Date;
        timeless_starts_at?: string;
        duration_minutes?: number;
        label_names?: string[];
        label_ids?: string[];
        metadata?: Record<string, any>;
        completed?: boolean;
        created_at?: Date;
        updated_at?: Date;
    }
  • TypeScript interface for the API response wrapper used in getTask return type.
    export interface ApiResponse<T> {
        data: T;
        success: boolean;
        error?: string;
        lists?: Record<string, TaskList>;
        labels?: Record<string, Label>;
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/AliNagy/godspeed-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server