Restore a specific Minecraft/Fabric bridge setting to its default value by supplying the setting name. Use it to undo configuration changes or recover standard behavior.
Reset a specific setting to its default value.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It states the effect (reset to default) but omits whether the operation is idempotent, reversible, permission-gated, or what happens if the setting name is invalid.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence with zero waste, front-loading the action and target. It is appropriately sized for a simple reset tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, 0% parameter schema coverage, and multiple sibling settings tools, the description is too thin. It lacks parameter meaning, usage context, and behavioral details, though the output schema covers return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for the single required parameter 'name'. The description says 'a specific setting' but adds no format, naming convention, or valid value guidance beyond what the parameter name already implies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'reset' and resource 'setting' with the target 'default value'. It distinguishes from 'set_setting' by implying restoration, but does not explicitly differentiate from sibling 'reset_all_settings' or clarify scope beyond 'specific'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like 'reset_all_settings' or 'set_setting'. The phrase 'a specific setting' implies single-setting scope but offers no explicit conditions, exclusions, or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.