Skip to main content
Glama

update_account_settings

Idempotent

Set your account theme to light, dark, or system. Requires OAuth account:write.

The website applies it on login, reload or return to its tab. This only
changes the theme; passwords, roles and sign-in providers cannot be changed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "theme": "<theme>"
    },
    "name": "update_account_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description adds value on top: the required OAuth scope (account:write), the fact that the change is deferred until page reload/login, and an explicit statement of what is NOT affected. This is exactly the extra behavioral context the structured fields cannot convey.

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?

Three short sentences, front-loaded with the action and allowed values, followed by the permission requirement and the effect scope. No filler and every sentence contributes new information.

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

Completeness5/5

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

For a single-parameter, non-destructive mutation with no output schema, the description covers the action, the legal values, the auth requirement, the application timing, and the mutation boundary. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema merely types `theme` as a bare string with no enum, so the description carries the full burden. It compensates completely by listing the three legal values, which the schema does not.

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

Purpose5/5

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

States a concrete verb and resource ('Set your account theme') and enumerates the accepted values (light, dark, system), so the agent knows exactly what the tool changes and can distinguish it from get_account_settings or set_account_username. The scope is unambiguous even though the tool name is broader than the single theme field.

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 useful context on when the change takes effect ('applies it on login, reload or return to its tab') and rules out adjacent actions ('passwords, roles and sign-in providers cannot be changed'). It never names an alternative sibling or states whether a read should precede it, so it falls just short of explicit when/when-not 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.