Google Jules MCP

jules_setup_wizard

Configure Google authentication for your deployment environment by detecting local or cloud setup and adjusting session preferences.

Instructions

Interactive session setup wizard for automated Google authentication configuration

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jules_setup_wizard"
  }
}

Input Schema

Name	Required	Description	Default
`environment`	No	Deployment environment (auto-detect will analyze current setup)
`preferences`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 2, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Without annotations, the description carries the burden of behavioral disclosure. It states the tool is interactive and for setup, but does not clarify if it modifies state, requires authentication, or has side effects. The interactive nature is implied but not elaborated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence, which is concise, but it lacks structure and does not expand on key aspects like parameters or behavior. It earns its place by stating purpose but could be more informative without adding length.

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

Completeness2/5

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

Given no output schema, no annotations, and nested parameters, the description is incomplete. It does not explain return values, side effects, or what the user should expect after running the wizard. Critical information for a setup tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (environment described, preferences sub-properties described but not the object itself). The description adds no additional meaning beyond what is in the schema, failing to explain parameter use or nuances like the impact of 'ease-of-use' vs 'performance' priorities.

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 as an 'Interactive session setup wizard for automated Google authentication configuration', specifying the verb (setup wizard) and resource (session with Google auth). It distinguishes from sibling tools by focusing on setup, not analysis or task management.

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?

No guidance is provided on when to use this tool versus alternatives like jules_session_info or jules_set_cookies. There is no mention of prerequisites, appropriate contexts, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server