lilbee

Overview Schema Source Related Servers Discussions Admin

settings_reset

Clear selected configuration keys so they fall back to environment, profile, or default values. Use it to remove custom overrides and restore inherited settings.

Instructions

Drop your values; env, profile or default applies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keys": "<keys>"
    },
    "name": "settings_reset"
  }
}

Input Schema

Name	Required	Description	Default
`keys`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.2Jul 22, 2026
- removedInput schema / properties / keys / title
```
Removed value: -"Keys"
```
- removedInput schema / title
```
Removed value: -"settings_resetArguments"
```
First observedv1.0.0Jun 15, 2026

TDQS

C2.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It hints that values are dropped and fallback precedence is env/profile/default, which is useful, but it does not say whether this is destructive, how permissions work, whether omitted or missing keys are affected, or what exactly gets reset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short, but it is cryptic and underspecified rather than efficiently structured. 'Drop your values; env, profile or default applies' is not a clear sentence and omits essential context for a tool of this complexity.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the description still leaves the required 'keys' parameter, usage context, and destructive/reset semantics undocumented. It provides one useful fallback-precedence detail but is not complete enough for an agent to call the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, 'keys', is required and has 0% schema description coverage, yet the description never mentions it. 'Your values' does not explain that the caller must supply an array of setting keys or what form those keys take.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Drop your values; env, profile or default applies' implies resetting settings values to environment/profile/default fallbacks, but it never explicitly names settings or the resource being affected. This is a vague purpose rather than a clear verb+resource statement, and it does not distinguish itself from the sibling 'reset' tool.

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?

There is no when-to-use guidance, no exclusions, and no comparison to settings_set or the generic reset sibling. The description gives no indication of the circumstances in which an agent should call settings_reset instead of those alternatives.

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