Skip to main content
Glama
Sign In
Gemini MCP Server

Gemini MCP Server

by salviz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

gemini_check_research

Check the status of deep research results or wait until they are complete, receiving a notification when finished.

Instructions

Check or wait for deep research results. Use wait=true to block until completion (ideal for background execution — the tool returns when research finishes, triggering a task notification in your AI client).

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": {
      "interactionId": "<interactionId>"
    },
    "name": "gemini_check_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoIf true, block and poll until research completes (default: false, single check)
interactionIdYesThe interaction ID returned by gemini_deep_research
timeoutMinutesNoMax wait time in minutes when wait=true (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It mentions blocking behavior and task notification, but lacks details on error handling, side effects, or what happens with invalid interactionId.

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?

Two sentences with no wasted words. The purpose is stated first, followed by usage guidance, making it front-loaded and efficient.

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 simplicity and full schema parameter descriptions, the description covers main behavior but omits return value details and error conditions, which is a gap without an output schema.

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?

Schema coverage is 100%, so baseline is 3. The description adds context for the wait parameter but does not significantly enhance meaning for interactionId or timeoutMinutes beyond 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?

The description clearly states the tool checks or waits for deep research results, distinguishing it from the sibling gemini_deep_research which initiates research. The verb 'check' or 'wait' and resource 'deep research results' are specific.

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 provides explicit guidance on using wait=true for background execution and indicates the tool returns upon completion. However, it does not explicitly state when not to use the tool or alternatives for other scenarios.

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