jev-docs-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jev_docs_listA | List every page in the official TypeSafe/Jev documentation (docs.typesafe.ai) with its path and one-line summary. Use this to discover what exists before reading. |
| jev_docs_searchA | Full-text search across the official TypeSafe/Jev documentation. Returns the best-matching pages with paths and snippets; pass a path to jev_docs_read for the full page. |
| jev_docs_readA | Read the full Markdown of one Jev documentation page. Accepts a path (e.g. 'primitives/noul'), a docs.typesafe.ai URL, or an exact page title. Long pages are paginated with offset. |
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
Each tool has a clearly distinct purpose: list enumerates all pages, search performs full-text lookup, and read fetches full page content. The descriptions explicitly clarify how they differ, leaving no realistic ambiguity.
All three tools follow the same predictable pattern: jev_docs_ prefix plus a consistent verb (list, search, read). There is no mixing of conventions.
Three tools is a well-scoped minimal set for a documentation server: discover, search, and read. Each tool earns its place without redundancy.
The surface covers the full read-only documentation lifecycle: discovery via list, targeted lookup via search, and full content retrieval via read with pagination support. No obvious gaps remain.