jev-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEV_SEARCH_MODEL | No | Model identifier. Defaults to `typesafe/jev-1.13` for OpenRouter and `jev-1.13.0` for TypeSafe. | typesafe/jev-1.13 |
| JEV_SEARCH_API_KEY | Yes | Your OpenRouter API key (or a TypeSafe-issued key when JEV_SEARCH_PROVIDER=typesafe). Required for real searches; dry_run does not need a key. | |
| JEV_SEARCH_PROVIDER | No | Provider to use: `openrouter` or `typesafe`. | openrouter |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jev_searchA | Complementary semantic search over lines of small text files. Returns every nonblank line with probability and match (>=0.5), plus source file and 1-based line. All selected lines leave the machine; a real search costs money. |
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 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose is clearly stated as semantic search over text file lines.
The single tool name 'jev_search' uses a clear snake_case convention with a domain prefix and action verb. With only one tool, there is no inconsistency to evaluate.
A single tool is borderline thin for a server, even if the server's apparent purpose is narrow. It covers the core search operation but provides no supporting operations.
The core semantic search operation is present and returns detailed results. Minor gaps exist, such as no way to limit results, filter files, or configure the match threshold, but these are workable.