Skip to main content
Glama

Get settings

get_settings
Read-only

The account's settings: display name, time zone, plan and AI credits left, the public profile posts go out under, the app preferences (spellcheck, word autocomplete), the tags in the sidebar, and the ready-made shelves with which are on. The theme is chosen per device and is not stored here.

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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-obvious scope information: the theme is per-device and deliberately not returned here, which prevents an agent from repeatedly querying for it. It does not discuss auth or freshness, but for a closed-world read that is minor.

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?

A single front-loaded sentence naming the resource, then a compact list of returned fields, closing with one exclusion. No filler and no repetition of structured data.

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?

There is no output schema, so the description carries the burden of describing return contents, and it does so by enumerating the setting groups. It stops short of describing the response's structure (flat object vs grouped) or whether values can be empty, which would help an agent consume the result.

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?

Zero parameters, so the schema baseline is 4. The description adds no parameter meaning because none exists, and correctly spends its words explaining the shape of the return instead.

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 names a specific resource ("The account's settings") and enumerates its contents, so an agent immediately knows this is the read of account-level configuration. It lacks an explicit verb ("Returns..."), but the implied read is unambiguous and no sibling tool overlaps this resource.

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 only implied: an agent must infer it should call this when it needs display name, plan, credits, preferences, tags, or shelf state. There is no explicit when-to-use statement, and it does not route to siblings that overlap partially (list_tags, list_folders) which return related data.

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