Skip to main content
Glama
routineco

Routine

Official
by routineco

calendarAll

Access and manage all calendars within the Routine MCP server to organize schedules, tasks, and notes efficiently.

Instructions

All calendars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'calendarAll' MCP tool. It sends an RPC request to 'calendar.all' with no parameters, returns the JSON-stringified response as text content, and handles errors by logging and returning an error message.
    server.tool("calendarAll", "All calendars.", {}, async ({}) => {
      try {
        const data = await sendRpcRequest("calendar.all", []);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching calendar.all: %o", error);
        return {
          content: [
            {
              type: "text",
              text: `Error fetching auth id: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    });
  • src/tools.ts:26-44 (registration)
    Registration of the 'calendarAll' tool using server.tool within the registerServerTools function.
    server.tool("calendarAll", "All calendars.", {}, async ({}) => {
      try {
        const data = await sendRpcRequest("calendar.all", []);
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      } catch (error) {
        logger.error("Error fetching calendar.all: %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)
    Invocation of registerServerTools, which registers all tools including 'calendarAll' on the MCP server.
    registerServerTools(server, sendRpcRequest, logger);
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 provides no information about what the tool actually does. 'All calendars' doesn't indicate whether this is a read operation, a write operation, what permissions might be required, what format the output takes, or any behavioral characteristics. This is completely inadequate for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just two words, this is a case of under-specification rather than effective conciseness. The description fails to convey essential information about the tool's purpose and behavior. Every word should earn its place, but these two words don't provide meaningful guidance to an AI agent.

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

Completeness1/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 and no output schema, the description 'All calendars' is completely inadequate. It doesn't explain what the tool does, what behavior to expect, what format results will take, or how it differs from sibling tools. Given the complexity of calendar operations and the lack of structured documentation, this description fails to provide the necessary context for an AI agent to use the tool effectively.

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 tool has zero parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to compensate for any parameter documentation gaps. The baseline for zero parameters is 4, as there are no parameters whose semantics need explanation beyond what the schema provides.

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

Purpose2/5

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

The description 'All calendars' is a tautology that essentially restates the tool name 'calendarAll' without specifying what action the tool performs. It doesn't indicate whether this tool lists, retrieves, displays, or manages calendars. While it identifies the resource (calendars), it lacks a clear verb to define the tool's function.

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 about when to use this tool versus alternatives. With sibling tools like 'calendarGet' and 'eventDay' available, there's no indication whether 'calendarAll' is for listing all calendars, retrieving all calendar data, or some other purpose. No context about prerequisites, timing, or exclusions is provided.

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