Skip to main content
Glama

settings_set

Update multiple configuration settings atomically with validation; failed changes roll back automatically, and cached data refreshes to reflect new values.

Instructions

Update one or more writable lilbee settings atomically.

Validates every key and value upfront; if any value fails validation
the entire batch rolls back and nothing is persisted. Successful
writes flush to ``config.toml`` and invalidate the in-process model
architecture, provider load, and API-key caches so the next call
observes the new configuration.

Args:
    updates: Map of setting key to new value. Pass ``null`` to clear
        a nullable field (falls back to the pydantic default on next
        process start). Numeric strings are coerced to int / float by
        pydantic; booleans accept ``true`` / ``false`` / ``1`` / ``0``.

Returns ``updated`` (the keys persisted) and ``reindex_required``
(true when one of ``chunk_size`` / ``chunk_overlap`` changed; the
caller should run ``sync(force_rebuild=true)`` to refresh the index).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses atomicity, validation, rollback, file persistence, cache invalidation, type coercion, and return values including reindex_required. This exceeds basic expectations for a mutation tool.

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?

The description is well-organized with separate sections for behavior, args, and returns, but is slightly verbose. Each sentence adds value, and the structure aids readability.

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?

Given the tool's complexity and lack of output schema, the description covers atomicity, validation, side effects (cache invalidation, file flush), and return behavior. It does not detail what happens with read-only settings or missing keys, but validation implies error handling.

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 coverage is 0% for the only parameter, but the description provides comprehensive details: map structure, clearing with null, numeric/boolean coercion, and implicit keys. This fully compensates for the schema gap.

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?

The description states 'Update one or more writable lilbee settings atomically,' clearly indicating the action (update) and resource (settings). It distinguishes from siblings like settings_get, settings_list, and settings_reset through the atomic update behavior.

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?

The description explains the atomic validation and rollback behavior, and notes when to run sync afterward. While it doesn't explicitly exclude use cases or mention alternatives, the context of sibling tools provides sufficient differentiation.

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/tobocop2/lilbee'

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