Skip to main content
Glama

update_settings

Change planning settings. For one-off absences (a free afternoon, a doctor's appointment) don't change working hours; tell the user to add a calendar event instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusEndNoEnd of the focus time, local HH:MM
focusStartNoStart of the focus time, local HH:MM
focusMorningNoWhether task work is preferably planned in the focus time (default 08:00–12:00). Only a preference: when more work is due, tasks also go to the rest of the working hours.
workingHoursNoPer ISO weekday "1".."7" a list of {start, end} local HH:MM ranges; a missing or empty day is off. Replaces all days, so send the full week.
personalHoursNoPersonal time outside working hours, when tasks with hoursType "personal" are planned. Same shape as workingHours; replaces all days.
maxLoadPercentNoHow much of each working day the plan may fill, meetings included
contiguousTasksNoWhether each task is planned as one block where it fits (default on), instead of being split to use gaps between meetings or the focus time. Only a preference: a task is still split when no free stretch is long enough, when it is longer than its maximum block length, or when keeping it whole would leave a working day empty.
maxBlockMinutesNoLongest block in one go for tasks without their own cap; null = no cap (the default), so a task may be planned in one piece. Don't set block limits if not specifically asked.
overtimePercentNoOvertime budget: share of the weekly working time (0 = off, the default; at most 50) in which tasks may also be planned in personal time, e.g. evenings, when they would not fit into working hours. Working hours are always used first, and fixed appointments stay where they are. Only change it when the user asks for it.
taskDistributionNopack (default): tasks are planned together, and with little work days at the end of the plan may stay free. spread: every working day of the first week gets some task work, also with few tasks, by moving tasks or splitting them. In both, a task too big for the gaps of a day is split rather than leave a day empty.
proposalThresholdNoHow many blocks an automatic replan may move or remove without asking; 0 = always ask
meetingBufferMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag this as a non-destructive mutation, so the description only has to reinforce intent. The extra context that one-off absences must not be modeled as permanent setting changes is genuinely useful behavioral guidance an agent would otherwise get wrong.

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?

Two sentences, the action first and the critical exclusion second, with no filler or repetition of schema content.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter partial-update tool with rich schema descriptions and no output schema, the description covers purpose plus the main misuse risk. A minor gap remains: it doesn't state that settings changes can affect existing plans or how they interact with replan behavior.

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 92%, with per-parameter semantics, defaults, and replace-vs-merge rules already documented, so the baseline of 3 applies. The description adds no parameter-specific meaning and doesn't restate that only supplied fields change.

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?

States a specific verb and resource ('Change planning settings'), which clearly separates it from the read counterpart get_settings and from task/habit mutation siblings. It doesn't enumerate which settings are covered, but the schema does that.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not case with a concrete alternative action: one-off absences should become calendar events rather than working-hours edits. It stops short of a general when-to-use statement (e.g. only after reading current settings) or naming get_settings as a prerequisite.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources