Skip to main content
Glama
vfa-khuongdv

MCP Chatwork Server

by vfa-khuongdv

get_my_tasks

List tasks assigned to the bot account, with optional filters for assigner account ID and task status (open or done).

Instructions

List tasks assigned to the current bot account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigned_by_account_idNoFilter by the account ID who assigned the task.
statusNoTask status (open or done).open

Implementation Reference

  • The main tool definition object with name ('get_my_tasks'), description, schema, and executor function that calls client.getMyTasks() and returns the result as JSON text content.
    export const getMyTasksTool = {
      name: "get_my_tasks",
      description: "List tasks assigned to the current bot account.",
      schema: GetMyTasksSchema,
      executor: async (client: ChatworkClient, args: z.infer<typeof GetMyTasksSchema>) => {
        const tasks = await client.getMyTasks(args.assigned_by_account_id, args.status);
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(tasks, null, 2),
            },
          ],
        };
      },
    };
  • Zod schema defining inputs: optional assigned_by_account_id (number) and optional status enum ('open'|'done') defaulting to 'open'.
    export const GetMyTasksSchema = z.object({
      assigned_by_account_id: z.number().optional().describe("Filter by the account ID who assigned the task."),
      status: z.enum(["open", "done"]).optional().default("open").describe("Task status (open or done)."),
    });
  • src/index.ts:74-82 (registration)
    Registration of the tool with the MCP server via server.tool(), using the tool's name, description, schema shape, and executor.
    server.tool(
      getMyTasksTool.name,
      getMyTasksTool.description,
      getMyTasksTool.schema.shape,
      async (args) => {
        // @ts-ignore
        return getMyTasksTool.executor(client, args);
      }
    );
  • API client method getMyTasks() that makes a GET request to /my/tasks with optional assigned_by_account_id and status query parameters.
    async getMyTasks(assignedByAccountId?: number, status: "open" | "done" = "open"): Promise<ChatworkTask[]> {
      try {
        const params: any = { status };
        if (assignedByAccountId) {
          params.assigned_by_account_id = assignedByAccountId;
        }
    
        const response = await this.client.get<ChatworkTask[]>("/my/tasks", { params });
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Chatwork API Error (Get My Tasks): ${error.message} - ${JSON.stringify(error.response?.data)}`);
        }
        throw error;
      }
    }
  • src/tools/index.ts:6-7 (registration)
    Re-export of the getMyTasksTool from the tools barrel module.
    export * from "./getMyTasks.js";
    export * from "./deleteMessage.js";
Behavior2/5

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

With no annotations, the description only states 'list tasks' without disclosing potential behavioral traits such as read-only nature, pagination, or rate limits. It relies on the verb 'list' to imply safety, but does not explicitly state mutability.

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 sentence that is concise and front-loaded, with no wasted words.

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 list tool with two optional parameters and no output schema, the description covers the basic purpose but leaves out details about response format and possible limitations.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for the two parameters.

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

Purpose5/5

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

The description clearly states the verb (list) and resource (tasks assigned to the current bot account), distinguishing it from sibling tools like create_task and complete_task.

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 explicit guidance on when to use this tool versus others. The description implies it's for listing tasks assigned to the bot, but does not mention alternatives or exclusion criteria.

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/vfa-khuongdv/mcp-chatwork'

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