Skip to main content
Glama

settings_list

List all writable settings with current values, defaults, types, and metadata, optionally filtered by group.

Instructions

List every writable lilbee setting with its current value and metadata.

Returns one row per setting with ``key``, ``value``, ``default``,
``type`` (``int``, ``float``, ``bool``, ``str``, ``list``, or a
``foo|null`` union), ``nullable``, ``group`` (Retrieval, Generation,
Models, Ingest, Wiki, Crawling, API-Keys, System, Display),
``help`` text, ``choices`` (for enum-typed fields), and
``reindex_required`` (whether changing the value invalidates the
persisted vector store).

Args:
    group: Filter by group name (case-insensitive). Empty = all.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, but the description thoroughly lists all returned fields and clarifies that the tool lists 'writable' settings, implying no destructive side effects. It could mention that it is read-only.

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 front-loaded with the core purpose, then details the return structure, then the parameter. It is slightly verbose but well-organized and every sentence adds value.

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

Completeness5/5

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

Given that an output schema exists (even if not shown), the description covers all essential elements: purpose, return fields, and parameter. For a list tool with one optional parameter, it is complete.

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 0% (no description in schema), but the tool's description explains the 'group' parameter fully: filter by group name, case-insensitive, empty returns all. This adds necessary meaning.

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 clearly states the action ('List') and resource ('every writable lilbee setting'), and distinguishes it from siblings like settings_get by implying a full enumeration.

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 implies usage for getting an overview of all settings, with an optional group filter. It does not explicitly contrast with settings_get or settings_set, but context from sibling names fills the gap.

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