gemini-jev-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | Yes | Your TypeSafe API key, stored separately in .secrets/TYPESAFE_API_KEY |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_statusA | Check local Gemini/Jev integration readiness without making paid requests or returning credentials. |
| delegate_taskA | Send one self-contained routine task to Gemini Flash, then batch-check its result with Jev. Supply selected absolute file paths and explicit acceptance criteria. Returns a short preview, full result file and review verdict. Cannot change source files, browse or execute commands. Uses Google quota and TypeSafe API credits. |
| jev_evaluateA | Ask Jev 1-12 narrow typed questions for routing, ranking or evidence checks on Codex/Gemini results. Supply context as text/JSON plus optional selected files. Confidence is advisory, not proof or authorization. Repeated identical evaluations are cached in this server process. Uses TypeSafe API credits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have largely distinct roles: bridge_status is a readiness probe, delegate_task runs a Gemini task with a Jev review, and jev_evaluate queries Jev directly. There is mild overlap since both delegate_task and jev_evaluate involve Jev evaluation, but the descriptions make the boundaries (full delegated workflow vs. narrow standalone questions) reasonably clear.
All names use snake_case, which is good, but the structural pattern is mixed: bridge_status is noun_noun, delegate_task is verb_noun, and jev_evaluate is a namespace-prefixed noun_verb. Readable and not chaotic, but not a predictable verb_noun convention throughout.
Three tools is slightly thin but appropriate for a narrow Gemini/Jev bridge whose scope is status checking, task delegation, and evaluation. Each tool earns its place without redundancy.
The surface covers the core bridge lifecycle: check readiness, delegate a task with review, and run standalone evaluations. Minor gaps exist (e.g., no way to cancel, poll, or manage in-flight delegated tasks), but agents can work around these for the stated purpose.