Skip to main content
Glama
Sign In
gemini-pro-mcp

gemini-pro-mcp

by Muzaqil555
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

jules_status

Read-only

Check a Jules session’s state, recent activities, questions, and any opened pull request; poll again while work continues.

Instructions

Check on a Jules session started with jules_start: its state, its most recent activities (plan, progress messages, questions, completion) and the pull request it opened, if any. Read-only and free; call it again to poll a session that is still working.

    Use jules_sessions to find a session id, jules_approve_plan when the state
    says it awaits plan approval, and jules_message to answer a question.

    Args:
        session: Session id from jules_start or jules_sessions, or its full
            "sessions/<id>" name or web link.
        activities: How many of the latest activities to show (default 15).

    Returns:
        The session title and state, any pull request links, and one line per
        recent activity with its time, kind and text.

Input Schema

NameRequiredDescriptionDefault
sessionYes
activitiesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description reinforces this with 'Read-only and free' while adding genuinely new context: the polling behavior for in-progress sessions. It stops short of stating rate limits or what happens for a nonexistent/expired session id, so it adds value but not full behavioral coverage.

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 opening sentence is front-loaded with purpose and scope, and the routing sentence follows logically. The Args/Returns docstring formatting is slightly verbose, and the Returns block partially restates what the output schema already provides, costing a bit of economy.

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?

For a two-parameter read tool with annotations and an output schema, nothing an agent needs to invoke it correctly is missing: accepted id formats, default activity count, sibling routing, and polling guidance are all present.

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?

Schema description coverage is 0%, so the description carries the full burden and does so: 'session' accepts a bare id from jules_start or jules_sessions, a full 'sessions/<id>' name, or a web link; 'activities' is the count of latest activities shown with a stated default of 15. This meaning is unavailable anywhere in the 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?

States a specific verb and resource ('Check on a Jules session started with jules_start') and enumerates what is retrieved: state, recent activities (plan, progress, questions, completion), and any pull request. This is clearly distinguishable from sibling tools like jules_sessions and jules_start.

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?

Explicitly routes the agent: use jules_sessions to find an id, jules_approve_plan when the state awaits plan approval, and jules_message to answer a question. It also states the polling pattern ('call it again to poll a session that is still working'), which is the key alternative to a one-shot check.

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