Skip to main content
Glama
mingovvv

tlc-portal-mcp

by mingovvv

auth.clear

Clear locally stored authentication sessions and JWT tokens to reset login state and log out of the portal.

Instructions

저장된 인증 세션을 삭제한다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The authClear handler function that executes the auth.clear tool logic. It calls auth.logout() to clear the session and returns the authentication status.
    export function authClear(
      auth: PortalAuthManager,
      sessionFile: string
    ): Record<string, unknown> {
      auth.logout();
      return {
        authenticated: false,
        hasJwtToken: false,
        sessionFile,
      };
    }
  • src/server.ts:67-72 (registration)
    Registration of the auth.clear tool with the MCP server. Defines the tool name, description (empty params schema), and wires it to the authClear handler.
    server.tool(
      "auth.clear",
      "저장된 인증 세션을 삭제한다.",
      {},
      () => toContent(authClear(auth, config.sessionFile))
    );
  • The logout() method in PortalAuthManager that is called by authClear. It clears the session store.
    logout(): void {
      this.store.clear();
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly identifies the destructive operation (deletion of sessions) but lacks critical context such as whether this affects only local state or server-side sessions, idempotency, or side effects on subsequent tool calls.

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?

The description consists of a single efficient sentence that immediately conveys the action and target. No redundancy or extraneous information present; front-loaded with the core operation.

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?

While adequate for a zero-parameter tool, the description lacks safety context expected for a destructive authentication operation given the absence of annotations and output schema. Should specify scope (local vs remote) and immediate consequences for user state.

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 input schema contains zero parameters (empty properties object), establishing baseline 4. The description appropriately requires no parameter explanation since the tool operates without inputs.

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?

The description provides a specific verb (삭제한다/deletes) and resource (저장된 인증 세션/saved authentication session). It clearly distinguishes this tool from sibling auth.login (which creates sessions) and auth.status (which checks sessions) by specifying the destructive clearing action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the destructive nature implies use for logout or credential reset scenarios, the description provides no explicit guidance on when to invoke this versus auth.login, nor does it mention prerequisites like requiring an active session or the consequences of clearing.

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/mingovvv/tlc-portal-mcp'

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