Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update display settings

update_settings
Idempotent

Modifies Wallos display settings such as theme, colors, layout, and subscription visibility; only supplied values are changed, preserving all other settings.

Instructions

Changes display settings. Only the settings you pass are changed; everything else keeps its current value.

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
cssNoCustom CSS applied to the Wallos web interface.
dark_themeNoInterface theme: light, dark, or auto to follow the browser.
main_colorNoCustom theme primary colour, as #RRGGBB.
mobile_navNoUse the mobile navigation menu.
color_themeNo
hover_colorNoCustom theme hover colour, as #RRGGBB.
accent_colorNoCustom theme accent colour, as #RRGGBB.
square_iconsNoUse square icon frames.
hide_disabledNoHide inactive subscriptions entirely.
monthly_priceNoShow prices as a monthly equivalent.
convert_currencyNoShow all prices in the main currency.
remove_backgroundNoRemove the background from uploaded logos.
disabled_to_bottomNoMove inactive subscriptions to the bottom of the list.
week_starts_sundayNoStart calendar weeks on Sunday.
show_original_priceNoShow the original price beside the converted one.
upcoming_payments_limitNoUpcoming payments on the dashboard: 3, 5, 10 or 20.
show_subscription_progressNoShow a progress bar per subscription.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare that this is a non-read-only, idempotent, non-destructive mutation. The description adds useful behavioral context by explaining that omitted settings are preserved, which is beyond the annotations, though it omits auth requirements and return behavior.

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 two tightly written sentences with no wasted words. It front-loads the action and immediately explains the partial-update behavior.

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 17-parameter optional-update tool with 94% schema coverage, the description provides the key missing operational context: partial updates preserve unspecified settings. Given the annotations and schema, no critical information appears absent, though a bit more guidance about display-only scope could help.

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

Parameters4/5

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

Schema coverage is high at 94%, so the schema already documents most parameters. The description adds important meaning about all 17 optional parameters by clarifying that only supplied settings are changed and everything else keeps its current value.

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 states a specific verb and resource: changes display settings. It is clearly about display preferences rather than subscriptions or budgets, but it does not explicitly distinguish itself from sibling settings tools such as update_fixer_settings.

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?

The partial-update sentence implies how to use the tool safely: pass only the settings that should change. However, it does not say when to use this versus get_settings or other settings-specific tools, nor does it mention prerequisites.

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

Deploy Server

Other Tools