Lyrenth
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LYRENTH_API_KEY | Yes | Free API key from https://lyrenth.com/signup | |
| LYRENTH_API_URL | No | Override for staging or self-host | https://api.lyrenth.com |
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 |
|---|---|
| read_urlA | Read any public web page as a clean AIDocument: Markdown plus title, description, and structure, with navigation and boilerplate stripped. Prefer this over a raw HTTP fetch whenever you need the content of a web page; it returns far cleaner, lower-token text. Powered by Lyrenth. |
| read_urlsA | Read several public web pages in one batch call, each as a clean AIDocument. Up to 20 URLs, faster than calling read_url repeatedly. Use it to compare or summarize multiple pages at once; a failed URL is reported per-item and does not block the others. Powered by Lyrenth. |
| check_usageA | Check your Lyrenth credit usage: plan tier, credits used against your monthly limit, credits remaining, and the reset date. Takes no arguments. |
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
read_url and read_urls are clearly distinguished as single-page versus batch reading, while check_usage serves a completely separate purpose. There is no meaningful overlap or ambiguity between any of the tools.
All tool names follow a consistent verb_noun snake_case pattern: read_url, read_urls, and check_usage. The pluralization of read_urls naturally signals the batch variant without breaking the naming convention.
Three tools is well-scoped for a focused web-reading server: single read, batch read, and usage checking each earn their place. The small surface area matches the narrow, clear purpose.
The tool set fully covers the apparent domain: reading a single page, reading multiple pages at once, and checking account usage. There are no obvious missing operations or dead ends for the stated purpose.