gemini-cli-bridge

by chaodongzhang

Overview Schema Source Related Servers Discussions Admin

Python

Local

Gemini Extensions List

gemini_extensions_list

List available Gemini CLI extensions to see which ones are installed or can be enabled.

Instructions

List available Gemini CLI extensions (gemini --list-extensions).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gemini_extensions_list"
  }
}

Input Schema

Name	Required	Description	Default
`timeout_s`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 20, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that this wraps the CLI command 'gemini --list-extensions', which implies a read-only enumeration, but says nothing about auth/permission needs, whether the CLI must be installed, or failure modes. With an output schema present, return values need not be explained.

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?

A single short sentence that front-loads the action and resource, with the parenthetical command adding useful grounding without waste.

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?

For a simple, side-effect-free listing tool with an output schema, the description covers what is needed to select and call it. The missing piece is any treatment of the timeout_s parameter and basic operational context (CLI availability/auth).

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

Parameters2/5

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

The single parameter timeout_s has 0% schema description coverage and is never mentioned in the description, so an agent gets no meaning, units, or default behavior for it beyond the schema's null default. For a 1-parameter tool with no compensating text, this is a clear gap.

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?

States a specific verb and resource ('List available Gemini CLI extensions') and even names the underlying command, so the agent knows this enumerates extensions rather than MCP servers or prompts. It does not explicitly contrast with the closest sibling (gemini_mcp_list), but the resource is distinct enough to disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternatives such as gemini_mcp_list. The name implies a read-only listing, but that is inference rather than stated guidance.

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