Skip to main content
Glama

getTaskLists

Fetch organized task lists from the Godspeed application via API. Manage and access task data efficiently within the godspeed-mcp server environment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYes

Implementation Reference

  • MCP tool handler for 'getTaskLists' that calls GodspeedAPI.getTaskLists(), stringifies the result as JSON text response, and handles errors.
    async () => {
        try {
            const result = await godspeedApi.getTaskLists();
            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)}` }]
            };
        }
    }
  • Input schema for the getTaskLists tool using Zod; requires a dummy 'random_string' parameter.
    {
        random_string: z.string()
    },
  • src/index.ts:209-226 (registration)
    Registration of the 'getTaskLists' MCP tool on the McpServer instance.
    server.tool(
        "getTaskLists",
        {
            random_string: z.string()
        },
        async () => {
            try {
                const result = await godspeedApi.getTaskLists();
                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)}` }]
                };
            }
        }
    );
  • GodspeedAPI class method implementing the core logic to fetch task lists via HTTP GET to /lists endpoint.
    async getTaskLists(): Promise<ApiResponse<TaskList[]>> {
        try {
            const headers = this.getAuthHeaders();
    
            const response = await fetch(`${API_BASE_URL}/lists`, {
                method: 'GET',
                headers,
            });
    
            const data = await response.json();
    
            if (!response.ok) {
                throw new Error(data.error || 'Failed to get task lists');
            }
    
            return data;
        } catch (error) {
            throw new Error(`Get task lists error: ${error instanceof Error ? error.message : String(error)}`);
        }
    }
  • TypeScript interface defining the structure of a TaskList returned by the API.
    export interface TaskList {
        id: string;
        name: string;
        created_at?: Date;
        updated_at?: Date;
    }
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