Skip to main content
Glama

google_calendar_set_default

Set a specific calendar ID as the default for Google Calendar operations using the Google MCP server.

Instructions

Set the default calendar ID for operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdYesThe ID of the calendar to set as default

Implementation Reference

  • Handler function that validates arguments and calls setDefaultCalendarId on the GoogleCalendar instance, returning the result.
    export async function handleCalendarSetDefault(
      args: any,
      googleCalendarInstance: GoogleCalendar
    ) {
      if (!isSetDefaultCalendarArgs(args)) {
        throw new Error("Invalid arguments for google_calendar_set_default");
      }
      const { calendarId } = args;
      const result = googleCalendarInstance.setDefaultCalendarId(calendarId);
      return {
        content: [{ type: "text", text: result }],
        isError: false,
      };
    }
  • Tool schema definition including name, description, and input schema requiring calendarId.
    export const SET_DEFAULT_CALENDAR_TOOL: Tool = {
      name: "google_calendar_set_default",
      description: "Set the default calendar ID for operations",
      inputSchema: {
        type: "object",
        properties: {
          calendarId: {
            type: "string",
            description: "The ID of the calendar to set as default",
          },
        },
        required: ["calendarId"],
      },
    };
  • server-setup.ts:92-96 (registration)
    Switch case in tool dispatch that routes 'google_calendar_set_default' to the calendar handler.
    case "google_calendar_set_default":
      return await calendarHandlers.handleCalendarSetDefault(
        args,
        googleCalendarInstance
      );
  • Core method in GoogleCalendar class that sets the default calendar ID and returns confirmation.
    setDefaultCalendarId(calendarId: string) {
      this.defaultCalendarId = calendarId;
      return `Default calendar ID set to: ${calendarId}`;
    }
  • Type guard function for validating arguments to google_calendar_set_default.
    export function isSetDefaultCalendarArgs(
      args: any
    ): args is { calendarId: string } {
      return args && typeof args.calendarId === "string";
    }
Behavior2/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. While 'Set' implies a mutation, it doesn't specify whether this change is persistent, reversible, requires specific permissions, or affects subsequent operations (like which calendar events are created in). This is inadequate for a mutation 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool and front-loads the essential information, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'default' means operationally, how to verify the change, or potential side effects. Given the complexity of setting a system-wide default, more context is needed for the agent to use this tool effectively.

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?

The input schema has 100% description coverage, with the single parameter 'calendarId' clearly documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., format examples, source of valid IDs, or scope implications), so it meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Set') and the resource ('default calendar ID'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'google_tasks_set_default_list' which performs a similar default-setting operation for a different resource, missing an opportunity for clear differentiation.

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 prerequisites (e.g., needing a valid calendar ID from 'google_calendar_list_calendars'), when this setting applies, or how it affects other operations, leaving the agent with insufficient context for proper tool selection.

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/vakharwalad23/google-mcp'

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