Skip to main content
Glama

chase_auth_clear

Reset Chase session cookies to log out and clear authentication state. Use this to end a session or troubleshoot authentication issues.

Instructions

Clear stored Chase session cookies. Use this to log out or reset authentication state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:59-67 (registration)
    Registration of the chase_auth_clear tool in the ListTools handler, defining its name, description, and empty input schema.
    {
      name: "chase_auth_clear",
      description:
        "Clear stored Chase session cookies. Use this to log out or reset authentication state.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Handler for chase_auth_clear tool execution: calls clearCookies() and returns a success message.
    case "chase_auth_clear": {
      clearCookies();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: true,
              message: "Chase session cleared. You will need to log in again.",
            }),
          },
        ],
      };
    }
  • Helper function that deletes the stored cookies file at ~/.strider/chase/cookies.json to clear the Chase session.
    export function clearCookies(): void {
      try {
        if (fs.existsSync(COOKIES_PATH)) {
          fs.unlinkSync(COOKIES_PATH);
        }
      } catch (error) {
        console.error("Failed to clear cookies:", error);
      }
    }
Behavior3/5

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

Without annotations, the description discloses the destructive nature (clearing cookies) but does not elaborate on reversibility or effects on subsequent operations. Adequate for a simple action but lacks depth.

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?

Two sentences with no waste. Front-loads the action and immediately gives use case. Perfectly concise.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters and no output schema, the description fully covers the tool's purpose and usage. No gaps remain.

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?

No parameters exist, so schema coverage is 100% trivially. The description adds no param info, which is acceptable since baseline for 0 params is 4.

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?

Clearly states the verb 'clear' and resource 'stored Chase session cookies', and equates it to 'log out or reset authentication state'. This distinguishes it from sibling tools like chase_auth_check, which checks auth state.

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?

States when to use it: 'to log out or reset authentication state'. Does not explicitly mention when not to use or alternatives, but the context is clear and the sibling tools provide implicit differentiation.

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/markswendsen-code/mcp-chase'

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