clear_sessionRemove the cached session token to sign out, ensuring subsequent API calls send no session header until a new session is established.
Forget the locally-cached session token (removes it from memory and the on-disk cache). After this, calls send no X-Api-Session header until you set_session again. Use it to sign out of the current session.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.1.6Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"v1.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the mutation nature (removes token from memory and disk cache) and the impact on subsequent calls (no X-Api-Session header). This goes beyond the annotations (readOnlyHint=false already indicates a write), providing concrete behavioral context about side effects and state change.
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?
Three sentences, each earning its place: the primary action, the consequence, and the explicit use case. The most important information is front-loaded, with no redundant or vague wording.
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?
For a simple tool with no parameters and no output schema, the description covers the action, side effects, and usage context. An agent has everything needed to invoke it correctly, including when to call it and what happens 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 tool has zero parameters, and the schema is empty (coverage 100%). Per calibration, a baseline of 4 is given for 0 params. The description does not add parameter-specific semantics, but none are needed since there are no parameters to document.
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 states a specific verb and resource: 'Forget the locally-cached session token' and clarifies the effect (removes from memory and disk cache). It explicitly positions itself as the counterpart to set_session by describing the absence of the X-Api-Session header afterward, making its purpose distinct among siblings.
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?
It gives a direct usage instruction: 'Use it to sign out of the current session.' It also explains the consequence (calls send no header until set_session again), which implicitly routes the agent to the appropriate sibling (set_session) for re-authentication. This is explicit enough for an agent to decide when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.