jevcrawl
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JEVCRAWL_MODEL | No | Model id. Pinned by default because thresholds are calibrated per version. | jev-1.13.0 |
| TYPESAFE_API_KEY | Yes | Jev API key (required). Get one from https://console.typesafe.ai/ | |
| JEVCRAWL_BASE_URL | No | Jev-compatible endpoint | https://api.typesafe.ai |
| JEVCRAWL_CACHE_DIR | No | Answer cache directory | ~/.jevcrawl/cache |
| JEVCRAWL_RENDER_JS | No | Render JavaScript-only pages when the js extra is installed (0 turns it off) | 1 |
| JEVCRAWL_RESPECT_ROBOTS | No | Skip URLs the site's robots.txt disallows (0 turns it off) | 1 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crawlA | Crawl a website toward a goal and return only the relevant passages, verbatim. Use this instead of fetching pages yourself when the answer may be several pages deep (documentation, help centers, policies, product catalogs). A small decision model scores every block of text and every link, follows the most promising links first, and stops as soon as the collected text answers the goal. No language model runs inside the crawl. Args: goal: A specific question to answer, e.g. "How many days do I have to get a refund?". Vague goals ("learn about the shop") return vague results. start_url: Where to start; the crawl stays on this host and its subdomains. max_pages: Page limit. Start with 10-30. max_seconds: Wall-clock limit. return_tokens: Most text (estimated tokens) to hand back. max_decision_usd: Hard limit on what the decision model may cost for this call. Returns:
Quote returned text together with its |
| scrapeA | Fetch one known page and return its text as blocks, optionally pruned to a goal. Without Returns the same shape as |
| mapA | Rank the URLs of a site by how likely they are to answer a goal, without returning content. Runs the same best-first exploration as Returns |
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 3 tools
The three tools have clearly distinct roles: crawl performs multi-page goal-directed exploration, scrape fetches one known page, and map ranks URLs without returning content. Although crawl and scrape can both accept a goal, the descriptions make the boundary explicit through link-following and page scope.
All tool names are concise lowercase verbs in a consistent style: crawl, scrape, map. There is no mixing of naming conventions or verb forms.
Three tools is a tight, well-scoped set for a goal-directed web crawling server. Each tool handles a distinct phase: discovery (map), single-page extraction (scrape), and multi-page retrieval (crawl).
The surface covers the full retrieval lifecycle for the stated domain: ranking URLs to explore, fetching a known page, and crawling multiple pages toward a goal. No obvious operational gap remains for the advertised web-crawling purpose.