Skip to main content
Glama

check_auth

Verify user authentication status to determine if ideas can be committed to IdeaLift. Use when connection issues prevent committing or to confirm account access before submission.

Instructions

Check the user's IdeaLift connection status for committing ideas.

Normalize is FREE. Commit requires connection.

USE this tool when:

  • User explicitly asks "am I connected?", "what's my status?", "check my account"

  • User is confused about why a commit isn't working

  • You need to verify auth before a create_ticket (commit) attempt

DO NOT use this tool when:

  • User is just chatting or exploring ideas (normalizing is free)

  • User is using normalize_idea (works without auth)

  • There's no indication of connection issues

Note: normalize_idea works WITHOUT auth. Only COMMITTING requires connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handleCheckAuth function executes the logic for the check_auth tool, performing authentication checks via the idealiftClient and handling OAuth linking if necessary.
    export async function handleCheckAuth(
      chatgptSubjectId?: string
    ): Promise<{ structuredContent: CheckAuthResult; content: string }> {
      const idealiftUrl = process.env.IDEALIFT_APP_URL || 'https://idealift.app';
    
      if (!chatgptSubjectId) {
        return {
          structuredContent: {
            authenticated: false,
          },
          content: `## Not Connected Yet
    
    Your ChatGPT session isn't linked to an IdeaLift account yet.
    
    **To connect:** Remove and re-add the IdeaLift app in ChatGPT settings — this will trigger the OAuth flow to link your workspace.
    
    In the meantime, you can use **normalize_idea** right now to structure your ideas — no account needed!
    
    **Try it:** Paste any rough idea and I'll normalize it into an execution-ready spec.`,
        };
      }
    
      try {
        let result = await idealiftClient.checkAuth(chatgptSubjectId);
    
        // If not authenticated, check if we have a valid OAuth token scoped to this subject
        if (!result.authenticated) {
          console.log('[Check Auth] Not authenticated, checking for scoped OAuth token...');
    
          const tokenInfo = await oauthService.getMostRecentTokenForSubject(chatgptSubjectId);
    
          if (tokenInfo?.workspaceId) {
            console.log('[Check Auth] Found scoped token, creating connection...', {
              chatgptSubjectId,
              workspaceId: tokenInfo.workspaceId,
              userId: tokenInfo.userId,
            });
    
            try {
              // Create the ChatGPT connection linking subject ID to workspace
              await idealiftClient.createConnection(
                chatgptSubjectId,
                tokenInfo.workspaceId,
                tokenInfo.userId
              );
    
              // Retry the auth check now that connection exists
              result = await idealiftClient.checkAuth(chatgptSubjectId);
              console.log('[Check Auth] Connection created, re-checked auth:', { authenticated: result.authenticated });
            } catch (connectError) {
              console.error('[Check Auth] Failed to create connection:', connectError);
            }
          } else {
            console.log('[Check Auth] No valid OAuth token found');
          }
        }
    
        if (result.authenticated) {
          return {
            structuredContent: result,
            content: `## Connected to IdeaLift ✓
    
    **Workspace:** ${result.workspaceName}
    **Plan:** ${result.plan}
    **Ideas remaining:** ${result.ideasRemaining} this month
    
    **Ready to commit ideas:**
    - Use **normalize_idea** to structure raw text into execution-ready specs
    - Use **list_destinations** to see your commit destinations
    - Use **create_ticket** to COMMIT ideas to GitHub/Jira/Linear
    
    **Need to connect more destinations?** Just ask to connect GitHub, Jira, or Linear.`,
          };
        } else {
          return {
            structuredContent: result,
            content: `## Account Found, Not Fully Connected
    
    Your IdeaLift account exists but isn't linked to this ChatGPT session.
    
    **To connect:** Remove and re-add the IdeaLift app in ChatGPT settings to trigger the OAuth flow, or visit [IdeaLift](${idealiftUrl}) to manage your account.
    
    In the meantime, you can still use **normalize_idea** to structure your ideas!`,
          };
        }
      } catch (error) {
        console.error('Check auth error:', error);
    
        return {
          structuredContent: {
            authenticated: false,
          },
          content: `## Connection Check Failed
    
    Couldn't verify your connection status. This might be temporary.
    
    **You can still:**
    - Use **normalize_idea** to structure ideas (no auth needed)
    - Try connecting again in a moment
    
    If this persists, visit [IdeaLift](${idealiftUrl}) directly.`,
        };
      }
    }
  • The checkAuthTool object defines the MCP tool name, description, and input schema for registration.
    export const checkAuthTool = {
      name: 'check_auth',
      description: `Check the user's IdeaLift connection status for committing ideas.
    
    Normalize is FREE. Commit requires connection.
    
    USE this tool when:
    - User explicitly asks "am I connected?", "what's my status?", "check my account"
    - User is confused about why a commit isn't working
    - You need to verify auth before a create_ticket (commit) attempt
    
    DO NOT use this tool when:
    - User is just chatting or exploring ideas (normalizing is free)
    - User is using normalize_idea (works without auth)
    - There's no indication of connection issues
    
    Note: normalize_idea works WITHOUT auth. Only COMMITTING requires connection.`,
      inputSchema: {
        type: 'object' as const,
        properties: {},
        required: [],
      },
      annotations: {
        readOnlyHint: false,    // Can create ChatGPT connection record if OAuth token exists but connection doesn't
        destructiveHint: false, // Only creates connection records, never deletes data
        openWorldHint: true,    // Calls IdeaLift API to verify authentication status
      },
      _meta: {
        'openai/visibility': 'public',
      },
    };
  • The CheckAuthResult interface defines the structure of the authentication status response.
    export interface CheckAuthResult {
      authenticated: boolean;
      workspaceName?: string;
      plan?: string;
      ideasRemaining?: number;
      authUrl?: string;
    }
Behavior4/5

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

Annotations indicate readOnlyHint: false, openWorldHint: true, destructiveHint: false. Description adds critical business logic beyond annotations: 'Normalize is FREE. Commit requires connection.' explaining the cost/auth implications. However, it doesn't explain why readOnlyHint is false despite 'check' typically implying read-only behavior, nor potential 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is excellent: purpose statement upfront, followed by business rule, then clear conditional sections (USE/DO NOT). Despite length, every sentence serves differentiation or guidance. No repetition of structured metadata.

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

Completeness4/5

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

Comprehensive for a zero-parameter tool with clear workflow integration. Minor gap: lacks description of return values (no output schema exists), though the intent of 'checking status' is reasonably inferable from the name and purpose.

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?

Tool accepts zero parameters (empty schema), warranting baseline score 4 per rubric. Schema coverage is trivially 100% for an empty object. No parameter clarification needed.

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?

Description opens with specific verb 'Check' and resource 'connection status', clearly scoped to 'committing ideas'. It distinguishes itself from siblings like normalize_idea and create_ticket by clarifying this validates commit capability, not normalization which works without auth.

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

Usage Guidelines5/5

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

Contains explicit 'USE this tool when' and 'DO NOT use this tool when' sections with specific scenarios. Explicitly names sibling tools (normalize_idea, create_ticket) to clarify boundaries and provides concrete user utterance examples ('am I connected?', 'why a commit isn't working').

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/Startvest-LLC/idealift-mcp-server'

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