Skip to main content
Glama

jules_session_info

Check current Google Jules AI coding assistant session configuration and authentication status to verify active connection and settings.

Instructions

Get current session configuration and authentication status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'jules_session_info' tool. It constructs and returns a JSON object containing the current MCP session configuration, including session mode, authentication methods available, browser status, and other runtime details.
    private async getSessionInfo(args: any) {
      const sessionInfo = {
        sessionMode: this.config.sessionMode,
        hasUserDataDir: !!this.config.userDataDir,
        hasCookiePath: !!this.config.cookiePath,
        hasGoogleAuthCookies: !!this.config.googleAuthCookies,
        hasBrowserbaseConfig: !!(this.config.browserbaseApiKey && this.config.browserbaseProjectId),
        browserbaseSessionId: this.config.browserbaseSessionId,
        isHeadless: this.config.headless,
        timeout: this.config.timeout,
        baseUrl: this.config.baseUrl,
        dataPath: this.config.dataPath,
        browserConnected: !!this.browser,
        pageReady: !!this.page
      };
    
      return {
        content: [
          {
            type: 'text',
            text: `Jules MCP Session Info:\\n${JSON.stringify(sessionInfo, null, 2)}`
          }
        ]
      };
    }
  • src/index.ts:389-390 (registration)
    Registration and dispatch of the tool handler within the CallToolRequestSchema switch statement in setupToolHandlers().
    case 'jules_setup_wizard':
      return await this.setupWizard(args);
  • src/index.ts:266-273 (registration)
    Tool registration in the ListToolsRequestSchema response array, defining the tool name, description, and input schema.
      name: 'jules_session_info',
      description: 'Get current session configuration and authentication status',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
    {
  • Input schema definition for the tool, specifying an empty object (no required parameters). Embedded within the tool registration.
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'authentication status,' which hints at read-only behavior, but doesn't clarify if this tool requires authentication itself, what data it returns (e.g., format, scope), or any side effects (e.g., rate limits, session updates). For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 is a single, clear sentence with zero waste. It's front-loaded with the core purpose ('Get current session configuration and authentication status'), and every word earns its place by specifying what is retrieved. No unnecessary details or redundancy are present.

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?

Given the tool's complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on return values, authentication requirements, or when to use it. Without annotations or output schema, more context on behavior and output would be helpful, but it meets the basic threshold for a simple tool.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any. Baseline for 0 parameters is 4, as it doesn't mislead or omit necessary param info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('Get') and resources ('current session configuration and authentication status'). It distinguishes itself from siblings like jules_get_cookies or jules_set_cookies by focusing on session configuration rather than cookie management. However, it doesn't explicitly differentiate from all siblings (e.g., jules_setup_wizard might relate to session setup).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether authentication is required to call it), when it's most useful (e.g., during session initialization or debugging), or what alternatives exist among siblings like jules_get_cookies for authentication details. Usage is implied but not explicitly stated.

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/mberjans/google-jules-mcp'

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