Skip to main content
Glama

Update my preferences

update_user_preferences
DestructiveIdempotent

Update your own UI preferences: default time-entry view, sub-views, theme, and time format. Only the fields you provide are changed (PATCH semantics). Applies to your account globally across all organizations. The user is fixed by your context — you can only change your own preferences.

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_user_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_formatNoClock format. One of: 12h, 24h.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
theme_preferenceNoUI theme preference. One of: light, dark, system.
default_day_sub_viewNoDefault sub-view for the day view. One of: timeline, list, stats, table.
default_week_sub_viewNoDefault sub-view for the week view. One of: calendar, list, timeline.
default_month_sub_viewNoDefault sub-view for the month view. One of: calendar, list, timeline.
default_time_entry_viewNoDefault time-entry view. One of: day, week, month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the safety profile is carried structurally. The description adds real value beyond that: PATCH semantics ('only the fields you provide are changed'), global cross-organization effect, and the self-only constraint that the user is fixed by context. It does not explain reversibility or why a preference write is flagged destructive, which is the remaining gap.

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

Conciseness4/5

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

Three short sentences, front-loaded with the resource and affected fields, then the PATCH contract, then scope. Nearly every clause earns its place; the final sentence's 'you can only change your own preferences' slightly restates the opening 'your own'.

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 7-parameter, all-optional mutation tool with full schema coverage and no output schema, the definition covers scope, partial-update semantics, and identity constraints. What remains unstated — reversibility of changes or failure behavior — is modest given the annotations already signal mutation and idempotency.

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% and all six enums are documented inline, so the schema does the heavy lifting on individual parameters. The description's only added parameter-level meaning is the PATCH contract that unspecified fields remain unchanged, which is useful but thin, so the baseline of 3 is appropriate.

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 gives a specific verb and resource ('Update your own UI preferences') and enumerates the exact fields affected: default time-entry view, sub-views, theme, and time format. The 'your own' framing implicitly separates it from update_user_profile and admin-oriented user tools, though no sibling is named outright.

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

Usage Guidelines3/5

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

Usage is implied by the scope constraints ('your own preferences', 'applies to your account globally'), which narrows when this tool is appropriate. However, there is no explicit when-to-use or when-not guidance and no named alternative, so the agent must infer the routing.

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