Skip to main content
Glama

consult_gemini

Read-only

Analyze a codebase by asking questions. Gemini autonomously reads files, lists directories, and searches code to provide answers, eliminating the need to pre-read files.

Instructions

Consult Gemini for codebase analysis.

Gemini autonomously explores our project — reading files, listing directories, and searching code — so we don't need to pre-read files. Just describe what we need. Use file_paths only when specific files must be included.

Pipeline: For auto, flash, and pro, Lite explores quickly first, then our selected model synthesizes. "lite" and explicit model IDs skip the exploration phase and query directly. Gemini's tools: list_directory, read_file, search_project, git, gemini_search; FileSearch stores are searched automatically when present.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe question or instruction
modelNo"auto" (default, Lite explore → Flash analyze), "flash", "pro", "lite", or full model IDauto
file_pathsNoLocal text files to read and include inline as context
media_pathsNoLocal image/PDF files (.png, .jpg, .webp, .gif, .pdf) for vision analysis
file_urisNoGemini File API URIs (from upload_file). Use for large files that exceed inline limits
json_modeNoReturn structured JSON output
response_schemaNoJSON schema string for structured output
cached_contentNoGemini context cache name
thinkingNoThinking level: "minimal", "low", "medium", "high", or None. Pro defaults to "high"
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds context about autonomous exploration, the pipeline (Lite explores then selected model synthesizes), and lists Gemini's internal tools, which enriches the behavioral model beyond annotations.

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 well-structured with clear sections and no fluff. Every sentence adds value, though it is slightly longer than necessary for the core purpose. It remains front-loaded with the most critical information.

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

Completeness4/5

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

Given the complexity and number of parameters, the description covers the tool's workflow and parameter usage quite well. It does not explain return values (no output schema), but the rest of the context is sufficiently complete for an agent to understand usage.

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

Parameters4/5

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

Schema coverage is 100% but the description adds meaning: explains 'auto' model behavior, that file_paths are for specific inclusions, and that thinking levels affect depth. This provides semantic value beyond the bare schema definitions.

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 it's for codebase analysis using Gemini, with autonomous exploration. However, it does not explicitly distinguish itself from the sibling tool 'consult_gemini_oneshot', which may have overlapping functionality.

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?

Provides guidance on when to use file_paths and explains the pipeline for different models. However, it lacks explicit when-not-to-use conditions or comparisons with sibling tools like gemini_search or consult_gemini_oneshot, leaving some ambiguity.

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/tobert/gpal'

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