Skip to main content
Glama

update_settings

Modify Pomodoro timer parameters including work duration, break intervals, and session cycles to customize productivity workflows.

Instructions

Update pomodoro timer settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workDurationNoWork duration in minutes
shortBreakDurationNoShort break duration in minutes
longBreakDurationNoLong break duration in minutes
pomodorosBeforeLongBreakNoNumber of pomodoros before long break

Implementation Reference

  • The handler logic for the 'update_settings' tool. It conditionally updates the pomodoro settings (workDuration, shortBreakDuration, longBreakDuration, pomodorosBeforeLongBreak) based on the input arguments, saves the data to the JSON file, and returns the updated settings.
    case "update_settings": {
      if (args.workDuration)
        data.settings.workDuration = args.workDuration as number;
      if (args.shortBreakDuration)
        data.settings.shortBreakDuration = args.shortBreakDuration as number;
      if (args.longBreakDuration)
        data.settings.longBreakDuration = args.longBreakDuration as number;
      if (args.pomodorosBeforeLongBreak)
        data.settings.pomodorosBeforeLongBreak =
          args.pomodorosBeforeLongBreak as number;
      saveData(data);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                success: true,
                settings: data.settings,
                message: "Settings updated successfully",
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • The tool registration and input schema definition for 'update_settings'. Specifies the name, description, and input schema with optional number properties for updating pomodoro timer settings.
    {
      name: "update_settings",
      description: "Update pomodoro timer settings",
      inputSchema: {
        type: "object",
        properties: {
          workDuration: { type: "number", description: "Work duration in minutes" },
          shortBreakDuration: {
            type: "number",
            description: "Short break duration in minutes",
          },
          longBreakDuration: {
            type: "number",
            description: "Long break duration in minutes",
          },
          pomodorosBeforeLongBreak: {
            type: "number",
            description: "Number of pomodoros before long break",
          },
        },
      },
    },
  • src/index.ts:245-247 (registration)
    Registers all tools, including 'update_settings', by setting the handler for ListToolsRequestSchema to return the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • Helper function called by the handler to persist the updated settings to the data file."},{
    function saveData(data: TodoPomoData): void {
      fs.writeFileSync(DATA_FILE, JSON.stringify(data, null, 2));
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't indicate whether this requires specific permissions, whether changes are immediate or require confirmation, what happens to active sessions during updates, or what the response looks like. For a settings mutation tool, this leaves significant behavioral questions unanswered.

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 - a single four-word phrase that communicates the core purpose without any wasted words. It's front-loaded and gets straight to the point, which is ideal for tool selection.

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 settings mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens when settings are updated (do active sessions reset?), what permissions are required, whether all parameters are optional (as indicated by 0 required parameters), or what confirmation/response to expect. The agent lacks critical context for proper tool invocation.

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 schema has 100% description coverage, with all four parameters clearly documented in the input schema. The description doesn't add any parameter-specific information beyond what's already in the schema. This meets the baseline expectation when schema coverage is complete.

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 ('Update') and the target resource ('pomodoro timer settings'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update_task', which also performs updates but on a different resource type (tasks vs. timer settings).

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. There's no mention of prerequisites, when settings updates are appropriate, or how this differs from other update operations like 'update_task'. The agent must infer usage context from the tool 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

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