askjev
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TYPESAFE_API_KEY | Yes | Your Typesafe API key used to authenticate with the Jev API. |
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 |
|---|---|
| askA | Ask Jev, a fast non-generative judgment model, one or more questions about some material you already have. Use it for a quick second opinion, a classification, a rating, or a yes/no check instead of reasoning it out yourself or spawning a sub-agent. Write each question in plain language. Jev decides whether it is a yes/no question, a scale, or a choice:
Every answer carries probabilities and Jev's confidence, plus "routing" showing how the question was interpreted. Read the confidence: a low value means the material does not settle the question, so add context or decide another way. Requires TYPESAFE_API_KEY in the server's environment. |
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
Only one tool exists, so there is no risk of an agent confusing it with any other. The ask tool has a clearly described purpose and modes.
With a single tool, there are no naming inconsistencies to evaluate. 'ask' is a simple, clear verb that matches the server's purpose.
One tool is on the thin end of the spectrum, explicitly in the borderline 1-2 range. However, the server's scope is narrow enough that this single tool is functionally sufficient.
The ask tool covers yes/no, choice, and scale questions with built-in rubrics and returns confidence and routing, covering the full intended domain. No obvious missing operations for a judgment-query server.