gemini-cli-bridge

by chaodongzhang

Overview Schema Source Related Servers Discussions Admin

Python

Local

Gemini Version

gemini_version

Retrieve the installed Gemini CLI version by running gemini --version and return it as JSON.

Instructions

Return installed gemini CLI version (gemini --version) as JSON.

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_version"
  }
}

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?

With no annotations, the description carries the full burden; it discloses the underlying mechanism (spawns `gemini --version`) and the return encoding (JSON), which is meaningful context. It omits that this is a non-destructive read, and says nothing about the timeout_s behavior or failure modes.

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?

One sentence, front-loaded with the action and resource, with the command equivalence in parentheses and the output format stated last. Nothing is wasted.

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?

An output schema exists, so return values need not be explained in prose. For a trivial zero-required-param probe, the description covers purpose, mechanism, and output format; only the timeout parameter is left unaddressed.

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?

Schema description coverage is 0% and timeout_s is undocumented in both schema and description. The description supplies no meaning for the single parameter, so it fails to compensate for the coverage 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: return the installed gemini CLI version. The parenthetical '(gemini --version)' makes the exact scope unambiguous, and no sibling covers version reporting. It does not, however, contrast itself with any sibling, which caps it below 5.

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?

No when-to-use or when-not-to-use guidance is given, and no alternatives are named. The intent ('check what version is installed') is inferable but only implied by the description text, so it lands at the no-guidance level.

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