read-website-fast
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_websiteA | Fast, token-efficient web content extraction - ideal for reading documentation, analyzing content, and gathering information from websites. Converts to clean Markdown while preserving links and structure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Cache Status | Get cache status information |
| Clear Cache | Clear the cache directory |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'read_website' has a clear, distinct purpose focused on web content extraction.
The single tool name 'read_website' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations to assess.
A single tool is generally too few for most server purposes, as it limits functionality and can feel thin. While the tool is well-described, the server's scope might benefit from additional related operations (e.g., for processing or analyzing the extracted content).
The tool covers the core function of reading websites effectively, but there are notable gaps for a broader web content domain. For example, there are no tools for updating, filtering, or managing multiple website reads, which could limit agent workflows.