Skip to main content
Glama

chat_gemini_hydrogen

Запрос к Gemini 4 Hydrogen (medium) через вашу подписку Google AI Pro.

    Старшая линейка Gemini 4: до 262144 токенов выхода у самой модели, есть
    уровень размышления `xhigh` (`gemini-4-hydrogen-xhigh`). Требует аккаунт,
    которому Hydrogen открыт: 404 от Google значит, что у подключённого
    аккаунта доступа нет — смотрите list_available_llm и переключайтесь
    через account_email. Варианты `-low` / `-high` / `-xhigh` доступны по
    точному id через OpenAI-совместимый `/v1/chat/completions`.

    Args:
        messages: список {"role": "user|assistant", "content": "..."}.
        system: системный промпт (опционально).
        max_tokens: максимум токенов в ответе (1..65536); размышления входят в лимит.
        thinking_budget: 0 — выключить, -1 — динамически, N — верхняя граница.
        thinking_level: "low" | "medium" | "high" | "xhigh" (приоритетнее thinking_budget).
        account_email: форсировать конкретный Google-аккаунт из пула.
        account_tag: форсировать аккаунты с указанным тэгом.

    Returns:
        {"text": str, "usage": {"input_tokens": int, "output_tokens": int}}.

    Raises:
        MCPError: ключ невалиден, Google не подключён, модели нет на аккаунте или квота исчерпана.
    

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": {
      "messages": "<messages>"
    },
    "name": "chat_gemini_hydrogen"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemNo
messagesYes
max_tokensNo
account_tagNo
account_emailNo
thinking_levelNo
thinking_budgetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare openWorld, non-idempotent, non-destructive behavior; the description adds account gating, 404 interpretation, quota/error raises, and return shape. It could go further on rate limits or nondeterminism, but it exceeds the annotation baseline.

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?

Front-loads the model identity and access constraint, then uses Args/Returns/Raises structure. A few details, such as exact alternate-id routing through /v1/chat/completions, are less relevant to invoking this MCP tool, but overall wording earns its place.

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 7 parameters, no schema descriptions, no output schema, and open-world model access, the definition covers invocation, return shape, and error cases well. It stops short of sibling-selection guidance, which keeps it from being fully complete.

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 coverage is 0%, so the description carries the full burden; it explains every argument including messages shape, max_tokens range, thinking_budget semantics, thinking_level priority, and account targeting. This is enough for an agent to populate parameters without schema descriptions.

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 request to Gemini 4 Hydrogen (medium) and identifies the model family and thinking-level variants. It distinguishes this model from the broader chat_gemini_* set by naming Hydrogen, though it does not explicitly compare when to choose it over siblings like chat_gemini_argon or chat_gemini_pro.

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?

Provides a clear prerequisite: a Google account with Hydrogen access, and tells the agent to inspect list_available_llm and switch via account_email on a 404. This is actionable context, but it does not explicitly say when this model is preferable to sibling chat tools or when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.