SearchForge
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_search | Search public sources and return ranked, deduplicated, citation-ready results. Use this for discovery across the web, GitHub repositories, academic works, or Hacker News; use read_url instead when a specific page URL is already known. This read-only operation may contact the selected third-party providers, so availability and rate limits depend on them. |
| read_url | Fetch one known public HTTP or HTTPS page and return clean, LLM-ready Markdown. Use this after web_search or when the exact URL is already known; do not use it to discover pages or access authenticated/private content. This read-only operation sends the URL to the configured reader service and can fail when the site blocks retrieval. |
| search_statusA | Probe every configured search provider and the URL reader, returning availability, latency, and failure details. Use this to diagnose SearchForge setup or provider outages, not to search for content. The probe is read-only but makes small external test requests that may count against provider rate limits. |
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 1 tool
With only one tool, there is no risk of confusion between tools. The tool's purpose is clearly distinct from any hypothetical other tools.
Only one tool exists, so naming consistency is trivially maintained. The name 'search_status' is clear and follows a predictable pattern.
The server is named SearchForge, implying search capabilities, but it contains only a diagnostic tool. One tool is far too few for the implied scope, resulting in a severe under-scoping.
The server completely lacks any search-related tools, which is its apparent core domain. The single tool is for health-check diagnostics, leaving a massive gap in functionality.