Skip to main content
Glama
routineco

Routine

Official
by routineco

taskUpcoming

Organize upcoming tasks by week and sort alphabetically for better task management within Routine's MCP server.

Instructions

Non-allocated organized by week and sorted alphabetically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the MCP tool 'taskUpcoming', which retrieves non-allocated tasks organized by week and sorted alphabetically by delegating to the backend RPC 'task.upcoming'. This is the core implementation of the tool's logic.
      "taskUpcoming",
      "Non-allocated organized by week and sorted alphabetically.",
      {},
      async ({}) => {
        try {
          const data = await sendRpcRequest("task.upcoming", []);
          return {
            content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
          };
        } catch (error) {
          logger.error("Error fetching task.upcoming: %o", error);
          return {
            content: [
              {
                type: "text",
                text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • src/tools.ts:864-886 (registration)
    Registration of the 'taskUpcoming' tool on the MCP server using server.tool, including empty parameter schema and the inline handler.
      "taskUpcoming",
      "Non-allocated organized by week and sorted alphabetically.",
      {},
      async ({}) => {
        try {
          const data = await sendRpcRequest("task.upcoming", []);
          return {
            content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
          };
        } catch (error) {
          logger.error("Error fetching task.upcoming: %o", error);
          return {
            content: [
              {
                type: "text",
                text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • src/index.ts:234-235 (registration)
    Call to registerServerTools which includes the registration of 'taskUpcoming' among other tools.
    registerServerTools(server, sendRpcRequest, logger);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions organization and sorting, implying a read-only operation, but doesn't disclose behavioral traits such as whether it requires authentication, has rate limits, or what the output format might be. This leaves significant gaps in understanding how the tool behaves.

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, efficient sentence that conveys the core function without waste. It's front-loaded with the main action, though it could be slightly more structured by specifying the resource type. Overall, it's appropriately sized for a simple tool.

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?

Given the tool's complexity (implied organization and sorting), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'non-allocated' means, what items are returned, or any behavioral aspects, making it inadequate for the agent to fully understand the tool's context and usage.

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?

The input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately doesn't add param details, but it does imply the tool operates on 'non-allocated' items, which adds minimal semantic context beyond the schema. Baseline is 4 for zero parameters.

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

Purpose3/5

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

The description states the tool organizes and sorts non-allocated items by week and alphabetically, which gives a vague purpose. However, it doesn't specify what type of items (e.g., tasks) or what 'non-allocated' means in context, and it doesn't clearly distinguish from siblings like taskDay or taskUnplanned, making it somewhat ambiguous.

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 context, prerequisites, or exclusions, and with siblings like taskDay and taskUnplanned, there's no indication of how this tool differs in usage, leaving the agent without clear 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

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

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