Skip to main content
Glama

Reset Context

reset_context

Clear all stored project context and restore defaults for a project directory, enabling AI assistants to start from a clean state.

Instructions

Reset the project context to default values (clears all data).

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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key trait that all context data is destroyed. It stops short of saying whether the wipe is irreversible, whether a confirmation is required, whether the path parameter scopes the destruction, or whether a backup is retained — all material for a destructive operation.

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?

A single short sentence with the destructive effect front-loaded in the parenthetical. Nothing is padding, though the phrasing could be tightened slightly.

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

Completeness3/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 described, and the lone parameter is fully documented in the schema. Still, for a destructive zero-annotation tool, the description should say what 'all data' covers (key files, tasks, decisions, context list) and whether the reset is recoverable.

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?

Schema description coverage is 100% with a single optional 'path' parameter already documented as the project root directory, so the baseline of 3 applies. The description adds nothing about how path interacts with the reset scope.

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

Purpose4/5

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

States a specific verb and resource ('Reset the project context') plus the outcome ('clears all data'), which is more than a restatement of the name. It does not, however, distinguish itself from nearby siblings such as init_context, reset_project_brain, or delete_path, which an agent must disambiguate on its own.

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 at all: no condition that selects reset over init_context, update_context, or reset_project_brain, and no note about prerequisites or confirmation. The agent must infer usage entirely from the name.

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