jev-studio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_instructionsA | Return the Jev ruleset for the given intensity (lite, full, or ultra). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| jev | Jev Studio instructions ruleset. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlapping purposes. The tool's purpose is singular and unambiguous.
The single tool name 'jev_instructions' follows a clear pattern with a prefix and a noun. Since there is only one name, there are no inconsistencies to evaluate.
A single tool feels too thin for a server named 'jev-studio', which implies a broader set of capabilities. Even for a specific function, one tool is on the extreme low end and likely insufficient for common agent workflows.
The tool covers all mentioned intensity levels (lite, full, ultra) and fulfills its stated purpose of returning a ruleset. No obvious gaps exist for this narrow scope, though additional related operations (e.g., listing available intensities) could enhance completeness.