Clears the context cache for a session to start with a clean slate.
Clears the context cache for a session, starting fresh.
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": "clear_context"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| session_id | No |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the context cache is cleared but does not state whether the operation is irreversible, what exactly is removed, whether it affects other sessions, or what the outcome is. The tool is a mutation, and these details are important for an agent to anticipate side effects.
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?
The description is a single, front-loaded sentence with no unnecessary words. It communicates the core action and scope immediately, making it easy to parse.
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?
The tool is simple—one optional parameter and no output schema—but the description omits behavioral details like side effects and return behavior. Given its simplicity, the description is minimally viable but leaves room for more context, such as what 'starting fresh' entails and what the agent should expect afterward.
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?
The schema has one parameter, session_id, with no description and 0% schema description coverage. The description mentions 'session' but does not explicitly link it to session_id, nor does it explain the expected format, optionality, or behavior when omitted. More parameter detail was needed in the description to compensate.
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?
The description clearly states the action ('Clears the context cache') and the scope ('for a session'), with a helpful qualifier ('starting fresh'). It is easily distinguished from sibling tools that route, plan, generate, or implement, as it is a utility to reset state.
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?
The phrase 'starting fresh' implies a usage scenario, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions. The context is simple enough that no alternatives conflict, but the description does not proactively explain when clearing context is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.