Skip to main content
Glama
routineco

Routine

Official
by routineco

taskDay

Organize daily tasks by priority: starred, default, completed, or ignored. Manage calendars, tasks, and notes efficiently with Routine’s integrated tools.

Instructions

Tasks of a day sorted by: starred < default < (completed or ignored).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYes

Implementation Reference

  • The handler function for the 'taskDay' tool. It takes a 'day' parameter (tuple of [year, month, day]), sends an RPC request to 'task.day', and returns the JSON-stringified response or an error message.
    async ({ day }) => {
      try {
        const data = await sendRpcRequest("task.day", [day]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching task.day: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for 'taskDay' tool defining the 'day' parameter as a tuple of three integers representing [year, month, day].
        {
          /*
    {"items":[{"$schema":"https://json-schema.org/draft/2019-09/schema","type":"integer"},{"$schema":"https://json-schema.org/draft/2019-09/schema","type":"integer"},{"$schema":"https://json-schema.org/draft/2019-09/schema","type":"integer"}],"$id":"#date","$schema":"https://json-schema.org/draft/2019-09/schema","type":"array"}
    */ day: z.tuple([z.number().int(), z.number().int(), z.number().int()]),
        },
  • src/tools.ts:776-803 (registration)
    Registration of the 'taskDay' MCP tool using server.tool(), including description, input schema, and handler function.
      server.tool(
        "taskDay",
        "Tasks of a day sorted by: starred < default < (completed or ignored).",
        {
          /*
    {"items":[{"$schema":"https://json-schema.org/draft/2019-09/schema","type":"integer"},{"$schema":"https://json-schema.org/draft/2019-09/schema","type":"integer"},{"$schema":"https://json-schema.org/draft/2019-09/schema","type":"integer"}],"$id":"#date","$schema":"https://json-schema.org/draft/2019-09/schema","type":"array"}
    */ day: z.tuple([z.number().int(), z.number().int(), z.number().int()]),
        },
        async ({ day }) => {
          try {
            const data = await sendRpcRequest("task.day", [day]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching task.day: %o", error);
            return {
              content: [
                {
                  type: "text",
                  text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
              isError: true,
            };
          }
        }
      );
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 of behavioral disclosure. It mentions sorting but doesn't cover critical aspects like whether this is a read-only operation, if it requires authentication, what happens with invalid input, or the response format. This leaves significant gaps for a tool with parameters.

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 functionality and sorting logic without unnecessary words. It's appropriately sized for a simple tool, though it could be more front-loaded by explicitly stating the action (e.g., 'Retrieve tasks for a day').

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 complexity (1 parameter with 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain the parameter's semantics, behavioral traits, or return values, making it inadequate for reliable tool invocation by an AI agent.

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

Parameters2/5

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

Schema description coverage is 0%, and the description provides no information about the 'day' parameter beyond implying it's used to specify a day. It doesn't explain the parameter's format (an array of three integers), purpose, or constraints, failing to compensate for the lack of schema documentation.

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 retrieves tasks for a specific day and mentions the sorting order (starred < default < completed/ignored), which clarifies the verb (retrieve/sort) and resource (tasks). However, it doesn't specify the exact action (e.g., 'retrieve' or 'list') or distinguish it from siblings like taskGet or taskUpcoming, making it somewhat vague.

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 such as taskGet, taskUpcoming, or eventDay. It lacks context on prerequisites, exclusions, or specific scenarios where this tool is preferred, leaving the agent to infer usage based on the name alone.

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