Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get display settings

get_settings
Read-only

Retrieves the account’s display preferences—theme, currency conversion, subscription ordering and hiding, and custom CSS—so you can inspect dashboard configuration.

Instructions

The account’s display preferences: theme, currency conversion, how subscriptions are ordered and hidden on the dashboard, and any custom CSS.

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": "get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=true already tell the agent this is a safe read against external account state. The description adds the useful detail that the settings are account-wide display preferences with no arguments, but says nothing about whether values are always populated, defaults for unset fields, or what happens for accounts without custom CSS.

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?

One compact sentence that front-loads the resource and enumerates the notable fields. It reads as a fragment rather than an action statement, which slightly reduces immediate clarity.

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?

With no parameters and no output schema, the description's job is to tell the agent what is returned, and it does that by naming the main preference categories. Minor gap: it does not state whether the response is a single flat object or note that update_settings is the write path.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly implies the call is scoped implicitly to the authenticated account.

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 enumerates the concrete contents of the resource (theme, currency conversion, subscription ordering/visibility, custom CSS), so an agent knows exactly what comes back. It is a noun phrase with no verb and never contrasts itself with update_settings, so sibling differentiation is left to the tool name.

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?

There is no when-to-use guidance and no pointer to update_settings as the mutation alternative, despite that sibling existing in the tool set. The agent must infer that this tool is the read counterpart.

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