Skip to main content
Glama
himomohi

aside-jev

by himomohi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TYPESAFE_API_KEYNoYour TypeSafe API key. Alternatively, set TYPESAFEAI_API_KEY instead.
TYPESAFEAI_API_KEYNoAlternative environment variable for the TypeSafe API key. Use either this or 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

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

Tools

Functions exposed to the LLM to take actions

NameDescription
jev_system_oneB

Call TypeSafe Jev with named questions. Each question uses type, instructions, criteria ONLY, never question or rubric. Score requires 2..64 ordered criteria from lowest to highest score. Noul uses true/false criteria descriptions. Example questions: {"completed":{"type":"noul","criteria":{"true":"The requested completion is visible","false":"Completion is absent"}}, "risk":{"type":"score","criteria":["No sensitive action","Reversible action","Sensitive or irreversible action"]}}. Report any error as an incomplete evaluation, never as overall success.

jev_chooseC

Choose an app-owned action ID. No action is executed by this tool.

jev_validateC

Validate a supplied candidate ID and return its original action payload.

jev_stepC

Choose, validate, and apply a confidence gate; return an execution payload.

jev_extension_statusA

Read the popup toggle state; this does not change settings or call Jev.

jev_browser_runA

Run observe → Jev → execute in one persistent Aside REPL session.

action_rules are explicitly authorized exact role/name/action rows; fill also
requires an explicit value. Never include an action needing ungranted user
approval. Supports click/focus/fill only. Uses live Jev, never a fallback LLM.
A completion_text and optional exact completion_url verify success locally.
Includes completion Noul and risk Score assessment after DOM completion.
verified is true only when both DOM and assessment pass; do not call a
separate assessment after success. On assessment_failed report partial
completion, never full success. Stops on stale observations and budgets.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

TDQS

C2.7/5.0

Scored across 6 tools

Disambiguation2/5

Several tools have overlapping responsibilities: jev_choose and jev_step both involve selecting an action, while jev_validate and jev_step both claim to validate. The descriptions help somewhat, but an agent could easily pick the wrong tool when choosing, validating, or executing a step.

Naming Consistency2/5

All tools share a jev_ prefix, but the rest of the names follow no consistent pattern: single verbs like validate/choose, noun compounds like extension_status/system_one, and an inverted noun-verb in browser_run. This mixed style reduces predictability and makes the API harder to navigate.

Tool Count4/5

Six tools is a reasonable size for a Jev/Aside-focused server, covering validation, evaluation, browser execution, extension status, and action selection. The count is not bloated, though some tools could potentially be consolidated.

Completeness3/5

The core workflow areas are represented: validation, system-one assessment, browser automation, and status reading. However, there is no obvious way to list available app-owned action IDs or modify extension settings, and the relationship between choose/step/validate leaves some workflow gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources