Skip to main content
Glama

settings_reset

Reset specified settings to their built-in defaults. Clears nullable fields and writes default values for non-nullable ones, invalidating relevant caches.

Instructions

Reset writable settings to their built-in defaults.

Nullable fields are cleared (the next process start falls back to
the pydantic default); non-nullable fields are written to disk with
their default value. Invalidates the same caches as ``settings_set``.

Args:
    keys: Setting keys to reset. Use ``settings_list`` to discover
        available keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. Explains difference between nullable and non-nullable fields, cache invalidation. Lacks auth requirements but still informative.

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?

Concise, well-structured with summary, behavioral details, and Args. Every sentence adds value, no fluff.

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 simple tool and existing output schema, description covers behavior, cache effects, and key discovery. Could clarify timing of reset but not a major gap.

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?

Despite 0% schema description coverage, the description in Args explains 'Setting keys to reset. Use settings_list to discover available keys,' adding meaning beyond the array type.

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?

Clearly states 'Reset writable settings to their built-in defaults.' Distinguishes from siblings like settings_set and settings_list, with a specific verb and resource.

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?

Explains when to use (reset to defaults) and points to settings_list for discovering keys. Doesn't explicitly state when not to use, but context is clear.

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