Skip to main content
Glama

start_pomodoro

Start a timed Pomodoro session for focused work, short breaks, or long breaks to enhance task management productivity.

Instructions

Start a new pomodoro session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdNoTask ID to work on (optional)
durationNoCustom duration in minutes (optional)
typeYesType of session

Implementation Reference

  • Handler function that starts a new pomodoro session based on the provided type (work, short-break, long-break), optionally for a specific task, using default or custom duration. Creates and saves a new PomodoroSession.
    case "start_pomodoro": {
      const type = args.type as "work" | "short-break" | "long-break";
      let duration: number;
      if (args.duration) {
        duration = args.duration as number;
      } else {
        switch (type) {
          case "work":
            duration = data.settings.workDuration;
            break;
          case "short-break":
            duration = data.settings.shortBreakDuration;
            break;
          case "long-break":
            duration = data.settings.longBreakDuration;
            break;
        }
      }
      const session: PomodoroSession = {
        id: Date.now().toString(),
        taskId: args.taskId as string,
        duration,
        type,
        startTime: new Date().toISOString(),
        completed: false,
      };
      data.sessions.push(session);
      saveData(data);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                success: true,
                session,
                message: `${type} session started for ${duration} minutes`,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Input schema definition for the start_pomodoro tool, specifying parameters like taskId (optional), duration (optional), and required type (work/short-break/long-break).
    {
      name: "start_pomodoro",
      description: "Start a new pomodoro session",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "Task ID to work on (optional)",
          },
          duration: {
            type: "number",
            description: "Custom duration in minutes (optional)",
          },
          type: {
            type: "string",
            enum: ["work", "short-break", "long-break"],
            description: "Type of session",
          },
        },
        required: ["type"],
      },
    },
  • src/index.ts:245-247 (registration)
    Registration of all tools including start_pomodoro via the ListToolsRequestSchema handler, which returns the TOOLS array containing the tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a state-changing action ('Start') but doesn't disclose what happens to existing sessions, whether it requires specific conditions, or what the response includes. This is inadequate for a tool that likely interacts with an active session state.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately clear without unnecessary elaboration.

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 and no output schema, the description is insufficient. It doesn't explain what starting a session entails (e.g., effects on other sessions, return values, or error conditions), leaving significant gaps in understanding how to use it 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?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning about parameters beyond implying a session initiation. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Start') and resource ('a new pomodoro session'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'complete_pomodoro' or 'get_active_session', but it's not misleading or tautological.

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?

No guidance is provided on when to use this tool versus alternatives like 'complete_pomodoro' or 'get_active_session'. The description only states what it does without context about prerequisites, timing, or relationships with other tools.

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

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/PratyayRajak/todopomo-mcp'

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