Skip to main content
Glama
routineco

Routine

Official
by routineco

eventTimeline

Generate an agenda view for a specific day using the Routine MCP server. Input a date to organize and manage events, tasks, and calendar details effectively.

Instructions

Agenda view for a day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes

Implementation Reference

  • Handler function that sends an RPC request to 'event.timeline' with the provided date tuple and returns the JSON-stringified response as text content, or an error message if failed.
    async ({ date }) => {
      try {
        const data = await sendRpcRequest("event.timeline", [date]);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching event.timeline: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema defining 'date' as a tuple of three integers representing year, month, and day.
    */ date: z.tuple([z.number().int(), z.number().int(), z.number().int()]),
  • src/tools.ts:150-176 (registration)
    MCP server.tool registration for 'eventTimeline', including description, input schema, and handler function.
        "eventTimeline",
        "Agenda view for a 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"}
    */ date: z.tuple([z.number().int(), z.number().int(), z.number().int()]),
        },
        async ({ date }) => {
          try {
            const data = await sendRpcRequest("event.timeline", [date]);
            return {
              content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
            };
          } catch (error) {
            logger.error("Error fetching event.timeline: %o", error);
            return {
              content: [
                {
                  type: "text",
                  text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
              isError: true,
            };
          }
        }
      );
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether it returns past/future events, or any rate limits. The description is completely silent on behavioral characteristics.

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 extremely concise with just four words, making it easy to parse quickly. There's no wasted language or unnecessary elaboration, though this brevity comes at the cost of completeness.

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?

For a tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what an 'agenda view' entails, what data it returns, how events are formatted, or any limitations. The minimal description leaves too many questions unanswered for effective tool use.

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?

The schema has 0% description coverage for its single 'date' parameter, and the tool description provides no information about what format the date array should be in (e.g., [year, month, day]), what timezone applies, or whether it accepts relative dates. The description fails to compensate for the complete 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 'Agenda view for a day' clearly indicates this tool displays events for a specific day, which is a specific purpose. However, it doesn't distinguish this from sibling tools like 'eventDay' or 'calendarGet', leaving ambiguity about how it differs from similar calendar/event tools.

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 like 'eventDay', 'calendarGet', or 'calendarAll'. It doesn't specify whether this is for personal calendars, shared calendars, or what type of events it displays, offering no contextual usage information.

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