Skip to main content
Glama

get_my_tasks_count

Get the count of your tasks filtered by type: responsible, ball holding, or following.

Instructions

指定したタイプの自分のタスク数を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesタイプ。responsible(担当)、ballHolding(ボール保持)、following(フォロー中)を指定できます。

Implementation Reference

  • Handler for 'get_my_tasks_count' tool in CallToolRequestSchema switch statement that calls RepsonaAPI.getMyTasksCount with the type argument and returns the count as JSON
    case 'get_my_tasks_count':
      const myTasksCount = await this.repsonaAPI.getMyTasksCount(args.type);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(myTasksCount, null, 2),
          },
        ],
      };
  • Schema definition for 'get_my_tasks_count' tool - requires a 'type' parameter with enum values: responsible, ballHolding, following
    {
      name: 'get_my_tasks_count',
      description: '指定したタイプの自分のタスク数を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          type: { 
            type: 'string', 
            enum: ['responsible', 'ballHolding', 'following'],
            description: 'タイプ。responsible(担当)、ballHolding(ボール保持)、following(フォロー中)を指定できます。' 
          },
        },
        required: ['type'],
      },
    },
  • index.js:828-842 (registration)
    Registration of 'get_my_tasks_count' tool in ListToolsRequestSchema handler's tools array, where the tool name is defined
    {
      name: 'get_my_tasks_count',
      description: '指定したタイプの自分のタスク数を取得します',
      inputSchema: {
        type: 'object',
        properties: {
          type: { 
            type: 'string', 
            enum: ['responsible', 'ballHolding', 'following'],
            description: 'タイプ。responsible(担当)、ballHolding(ボール保持)、following(フォロー中)を指定できます。' 
          },
        },
        required: ['type'],
      },
    },
  • API helper method in RepsonaAPI class that makes an HTTP GET request to /me/task/{type}/count endpoint to get the count of tasks for a given type
    async getMyTasksCount(type) {
      return this.makeRequest(`/me/task/${type}/count`);
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the basic operation. It fails to mention that this is a read-only operation, any authentication needs, or potential performance implications.

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, front-loaded sentence that conveys the core purpose efficiently. While concise, it could be more structured by separating the verb and resource.

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

Completeness2/5

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

Without an output schema, the description should explicitly mention the return value (a number) and any edge cases. It also lacks context about error handling or when the count is zero, leaving the agent with incomplete information.

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% with detailed enum descriptions. The description adds no additional meaning beyond what the schema already provides, so it meets the baseline of 3.

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 it retrieves the count of the user's own tasks of a specified type, using a specific verb and resource. It distinguishes itself from sibling tools like get_my_tasks (which returns task list) and get_inbox_unread_count (which counts inbox items).

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 (e.g., get_my_tasks for detailed task data). It does not mention when a count is appropriate instead of fetching full task lists.

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/bellx2/repsona-mcp-server'

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