Skip to main content
Glama
archolet

Claude Gemini Bridge

by archolet
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

maestro_start_session

Initiates a guided design session where an AI wizard interviews you about your project to automatically select design mode and parameters. Accepts a design brief for brand soul extraction and context-aware questions.

Instructions

Start a new MAESTRO design wizard session.

MAESTRO asks intelligent questions to understand your design needs and automatically selects the best design mode and parameters.

This is the entry point for the guided design workflow. MAESTRO will ask a series of questions about your intent, scope, theme preferences, and then generate a design decision.

NEW in v2: If a design_brief is provided, MAESTRO uses AI to extract the project's "soul" (brand personality, target audience, visual language) and generates dynamic, context-aware questions to fill gaps.

Args: project_context: Project description for context (e.g., "B2B SaaS dashboard for Turkish fintech startup"). Helps MAESTRO make better design decisions. existing_html: Optional existing HTML for refinement or style matching. If provided, MAESTRO may suggest refine_frontend or design_section modes. design_brief: Optional design brief for soul extraction (v2 feature). When provided, MAESTRO analyzes the brief to understand brand personality, target audience, and visual preferences, then asks only the questions needed to fill gaps. Example: "Modern fintech app for millennials. Professional but approachable. Blue/purple gradient theme preferred."

Returns: Dict containing: - session_id: Unique session identifier (use this for subsequent calls) - question: First interview question with id, text, category, options - progress: Interview progress (0.0 to 1.0) - status: "interviewing" | "decided" | "failed" - v2_enabled: Whether soul-aware v2 mode is active (only if design_brief provided) - soul_confidence: Confidence score of soul extraction (0.0-1.0, only in v2)

Example: # Start a new design session with design brief (v2) result = await maestro_start_session( design_brief="E-commerce product page for Turkish market. " "Target: young professionals. Tone: modern, trustworthy.", project_context="E-commerce product page" ) session_id = result["session_id"] # Answer the first question using maestro_answer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
design_briefNo
existing_htmlNo
project_contextNo

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It details the interactive flow, v2 soul extraction feature, and return fields. It does not mention rate limits or resource usage, but the level of detail is sufficient for safe invocation.

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

Conciseness4/5

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

The description is fairly lengthy but well-structured with summary, explanation, Args, Returns, and Example sections. It is front-loaded with the main purpose, and each sentence adds value. Minor redundancy could be trimmed.

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 no output schema, the description includes a comprehensive Returns section with all fields. It explains the tool's role among 19 siblings, mentions v2 features, and provides an example that shows session flow. Complete for a session-starting tool.

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

Parameters5/5

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

Despite 0% schema description coverage, the description provides detailed explanations for all three parameters in a dedicated Args section, including examples and effect on behavior (e.g., design_brief triggers v2). This compensates well for the sparse schema.

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 clearly states the tool starts a new MAESTRO design wizard session, serving as the entry point for the guided design workflow. It uses specific verbs like 'Start' and distinguishes its role from sibling tools like maestro_answer and maestro_abort.

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?

The description explains that this is the entry point, and provides context for when to provide design_brief or existing_html, and mentions that MAESTRO may suggest alternative modes. It does not explicitly state when not to use it but the example shows the next step (maestro_answer).

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/archolet/claude-gemini-bridge'

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