url-text-fetcher
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_url_textB | Download the text from a URL. |
| fetch_page_linksB | Return a list of all URLs found on the given page. |
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 fetches the text content of a URL, the other extracts links from a page. There is no overlap or ambiguity between them.
Both tool names follow the verb_noun pattern consistently: fetch_url_text and fetch_page_links. The naming is clear, predictable, and uniform.
With only two tools, the set feels thin. While the scope is narrow and both tools are useful, this falls at the borderline where 1-2 tools are considered minimal.
For a URL text fetcher, the two tools cover the primary needs: retrieving the text content and discovering links on a page. The surface is complete for this simple, read-only domain, with no obvious gaps.