Skip to main content
Glama
ctmx

openrouter-jev-mcp

by ctmx

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JEV_LOG_DIRNoDirectory where diagnostic logs are written. Defaults to ~/.local/state/jev-gateway.~/.local/state/jev-gateway
OPENROUTER_API_KEYYesYour OpenRouter API key used to access the Jev model through OpenRouter's Decisions endpoint.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
jev_checkC

Evaluate a Noul proposition against string, object, or list state.

jev_classifyC

Choose one caller-defined label for string, object, or list state.

jev_scoreC

Score string, object, or list state against ordered caller-defined levels.

jev_evaluateC

Evaluate a named map of Noul, Choice, and Score questions.

jev_healthA

Report OpenRouter configuration readiness; connectivity is unverified unless explicitly probed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a distinct evaluation purpose: single check, classification, scoring, batch evaluation, and health reporting. The only mild overlap is between jev_check and jev_evaluate, since evaluate can contain Noul questions, but the singular versus map distinction keeps them separable.

Naming Consistency4/5

All tools share the jev_ prefix and use lowercase snake_case, creating a clear family resemblance. The main inconsistency is that four tools are verb-based (check, classify, score, evaluate) while jev_health is a noun, but the pattern remains predictable.

Tool Count5/5

Five tools is a well-scoped set for an evaluation-oriented server: single operations plus a batch operation plus health. Each tool has a distinct role without unnecessary redundancy.

Completeness5/5

The tool surface covers the core evaluation lifecycle: primitive checks, categorical classification, ordered scoring, batched evaluation of mixed question types, and health/configuration readiness. No significant dead ends or missing core operations are apparent for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues