Skip to main content
Glama

Clear the runtime personality override (gated)

reset_personality

Clears a temporary session-scope personality override and restores the durable default style settings; use it when you want to drop a temporary style change.

Instructions

Clear any temporary (session-scope) personality override and revert to the durable default dials. GATED (one-time approval). Does not change the durable defaults themselves. Call this when the owner wants to drop a temporary style change.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reset_personality"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose two important traits: the operation is gated behind one-time approval, and it leaves durable defaults untouched. It omits what happens when no override exists (idempotency) and what the response looks like, but the core behavioral picture is clear.

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?

Front-loaded with the action and scope, followed by the gate and the non-destructive caveat. The final sentence slightly restates the first ('drop a temporary style change' vs. 'Clear any temporary ... override'), but it adds the actor ('the owner') rather than being pure repetition.

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 zero-parameter, no-output-schema tool the description covers what is cleared, what is preserved, and the approval gate. Only the no-op/empty-state behavior is unstated, which is a small gap for a tool this simple.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and nothing for the description to compensate for. Baseline 4 applies.

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?

States a specific verb ('Clear'), a precise resource ('temporary (session-scope) personality override'), and the resulting state ('revert to the durable default dials'). The clause 'Does not change the durable defaults themselves' separates it from durable-edit siblings such as propose_brain_edit or set_trait without needing their schemas.

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?

Gives an explicit trigger: 'Call this when the owner wants to drop a temporary style change.' The scope caveat implies when not to use it (durable changes need a different tool), but no alternative tool is named, so the routing is inferred rather than spelled out.

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