Skip to main content
Glama

reset_learned_weights

Reset all learned weights to erase accumulated training. Requires explicit confirmation via the confirm parameter.

Instructions

Reset all learned weights.

WARNING: This erases all accumulated learning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be True to confirm the reset

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description explicitly warns that the action erases all accumulated learning, disclosing its destructive nature. Since no annotations are provided, this is essential behavioral context beyond the schema. However, it does not mention the confirmation parameter or other side effects, though the schema covers confirmation.

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?

The description is exceptionally concise, with just two sentences: the primary action and a clear warning. It is front-loaded with purpose and includes a critical warning, with no wasted words.

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?

For a tool with a single parameter and an output schema, the description covers the core purpose and the critical destructive behavior. The confirmation requirement is documented in the schema, so the description need not repeat it. A minor gap is not stating what happens if confirm is false, but that is inferable from the schema.

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

Parameters3/5

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

The schema fully describes the confirm parameter with 'Must be True to confirm the reset', and the description adds no additional parameter-specific meaning. With 100% schema description coverage, the baseline of 3 is appropriate.

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 it resets all learned weights, which is a specific verb+resource action. It distinguishes from sibling tools like get_learned_weights (which reads) and refresh_tool_index (which refreshes indexes), making the purpose unmistakable.

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?

The description gives no explicit guidance on when to use the tool versus alternatives, nor any exclusions or prerequisites. The warning implies caution but does not specify a usage context or compare with other tools.

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/Rixmerz/proxy-mcp'

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