Better Fetch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | The Node.js environment mode | production |
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 |
|---|---|
| fetch_website_nestedC | Fetch website content with nested URL crawling and convert to clean markdown |
| fetch_website_singleB | Fetch content from a single webpage and convert to clean markdown |
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 2 tools
The two tools have clearly distinct purposes: one handles single-page fetching while the other includes nested URL crawling. The descriptions explicitly differentiate between these scopes, leaving no room for confusion or misselection.
Both tools follow a consistent verb_noun pattern with 'fetch_website' as the base, differentiated by descriptive suffixes ('_single' and '_nested'). This predictable naming makes it easy to understand their relationship and functionality.
With only two tools, the server feels under-scoped for a 'Better Fetch' purpose. While the tools cover basic fetching scenarios, there are likely missing operations like handling authentication, adjusting fetch parameters, or error management that would be expected in a robust fetching toolset.
For a fetching domain, the toolset is severely incomplete. It lacks essential operations such as configuring fetch options (e.g., headers, timeouts), handling different content types, managing errors, or providing status information. This will likely cause agent failures when dealing with complex fetching tasks.