beacon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEACON_TIMEOUT | No | HTTP timeout (seconds) for fetch | 15 |
| BEACON_LOG_LEVEL | No | Logging verbosity | INFO |
| BEACON_USER_AGENT | No | User-Agent for outbound requests | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 |
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 |
|---|---|
| beacon_searchA | Search the web (DuckDuckGo) and return ranked results. Use this to discover URLs for a topic. Then call beacon_fetch on the most relevant URL to read its content. Args: query: Search terms. max_results: Max hits to return (1..20, default 5). Returns: List of {"title", "url", "snippet"} objects. |
| beacon_fetchA | Fetch a URL and return its main readable text content. Extracts the article/page body (drops navigation, ads, boilerplate). Returns plain text, not HTML. Args: url: An http(s) URL. max_chars: Truncate content to protect context budget (default 8000). Returns: {"url", "title", "content"} or None if the URL cannot be fetched. |
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 searches the web for URLs and the other fetches a specific URL's content. There is no overlap or confusion between them.
Both tools use a consistent 'beacon_' prefix followed by a simple verb ('search' and 'fetch'), forming a predictable and coherent naming pattern.
With only two tools, the server feels minimally scoped for a web search/fetch utility. While each tool is essential, the count is borderline and may leave users wanting additional capabilities like URL validation or cached results.
The server provides a complete workflow: search for URLs, then fetch and read content. It covers the core domain of web searching and extraction without obvious gaps or dead ends.