Skip to main content
Glama
Sign In
Claude Gemini Bridge

Claude Gemini Bridge

by archolet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

maestro_get_progress

Retrieve visual progress updates for an active session: progress bar, percentage, current step, total steps, and category-specific tips.

Instructions

Get rich formatted progress display for a session.

Phase 6 feature: Returns visual progress information including:

  • Progress bar with percentage

  • Current step indicator

  • Category-specific tips

Args: session_id: Active session ID

Returns: Dict containing: - progress_bar: Visual ASCII progress bar - percentage: Progress as percentage string - current_step: Current step number - total_steps: Estimated total steps - category_tip: Helpful tip for current category

Example: progress = await maestro_get_progress(session_id="maestro_abc123") print(progress["progress_bar"]) # ████████░░░░░░░░ 50%

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "maestro_get_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It details the return structure (progress bar, percentage, current_step, total_steps, category_tip) and gives an example. However, it does not explicitly state that the operation is read-only or discuss side effects, which would raise transparency further.

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 well-structured with clear headings (Args, Returns, Example) and is concise. Every sentence adds value; there is no redundancy or fluff. The example further enhances clarity without unnecessary length.

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?

Despite no output schema and no annotations, the description fully covers the tool's purpose, parameters, return values, and provides an example. For a simple retrieval tool with one parameter, this is complete and demonstrates strong contextual coverage.

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

Parameters3/5

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

The input schema has 0% description coverage for the single parameter 'session_id'. The description adds 'Active session ID' which provides basic semantics but does not elaborate on format or constraints. The baseline of 3 is appropriate given the low coverage and minimal compensation.

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 uses a specific verb 'Get' and clearly identifies the resource 'rich formatted progress display for a session'. It distinguishes itself from sibling tools like 'maestro_get_decision' and 'maestro_get_analytics' by focusing on progress tracking.

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?

The description includes 'Phase 6 feature' hinting at context but does not explicitly state when to use this tool over alternatives. No when-not-to-use or alternative suggestions are provided, leaving usage largely implied.

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

Deploy Server

Other Tools