Skip to main content
Glama

get_settings

Retrieve user preferences and settings for your Remember The Milk account. Access current configuration values.

Instructions

Get user settings.

Returns: User preferences and settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_settings' tool. It calls rtm.settings.getList via the RTM client and formats the response with timezone, date_format, time_format, default_list_id, language, and raw settings.
    @mcp.tool()
    async def get_settings(ctx: Context) -> dict[str, Any]:
        """Get user settings.
    
        Returns:
            User preferences and settings
        """
        from ..client import RTMClient
    
        client: RTMClient = await get_client()
    
        result = await client.call("rtm.settings.getList")
    
        settings = result.get("settings", {})
    
        # Format settings nicely
        date_format = (
            "European (DD/MM/YY)" if settings.get("dateformat") == "0" else "American (MM/DD/YY)"
        )
        time_format = "12-hour" if settings.get("timeformat") == "0" else "24-hour"
    
        return build_response(
            data={
                "timezone": settings.get("timezone"),
                "date_format": date_format,
                "time_format": time_format,
                "default_list_id": settings.get("defaultlist"),
                "language": settings.get("language"),
                "raw": settings,
            },
        )
  • The registration function that uses @mcp.tool() decorator on get_settings to register it as an MCP tool.
    def register_utility_tools(mcp: Any, get_client: Any) -> None:
        """Register utility and diagnostic tools."""
  • Server main entry point calls register_utility_tools(mcp, get_client) which registers the get_settings tool.
    register_utility_tools(mcp, get_client)
Behavior2/5

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

No annotations provided; description only states it 'Returns user preferences and settings'. It fails to disclose behavioral traits like authentication needs, side effects, or read-only nature.

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?

Extremely concise with one clear sentence and a return description. Every word is purposeful; no redundancy.

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

Completeness3/5

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

Given the presence of an output schema, the description need not detail return values. However, it lacks any contextual completeness such as prerequisites or usage hints, making it adequate but minimal.

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?

No parameters exist, so schema coverage is 100%. The description adds no meaningful value beyond the schema, warranting the baseline score of 3.

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?

Description clearly states 'Get user settings', a specific verb+resource. It distinguishes from sibling get_* tools (e.g., get_contacts, get_lists) by targeting settings specifically.

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?

No guidance on when to use this tool versus alternatives. The description does not mention contexts, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ljadach/rtm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server