searchpin
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web via multiple engines (Baidu, Sogou, Bing CN, Bing Intl). Returns ranked titles, URLs, and snippets (no full page content — use web_fetch to get the full text of any result). Baidu searches are spaced by at least 20 seconds per server process. A Baidu captcha pauses only Baidu for 600 seconds; other engines can still return results. If search_pages reports off_topic_headword, the source returned dictionary entries about only part of the query. Refine the search using distinct terms, another language or an official domain. HTTP errors are reported in http_status. In search_pages, paced means the local interval skipped a source; cooldown means it is temporarily paused. Results re-ranked by embedding similarity — the top results are the most relevant. Iterative search is normal: search → read → refine → search → read → synthesize. Search returns only titles + snippets. Read snippets to identify promising results, then call web_fetch to get full page content for the URLs that look most useful. BEFORE FETCHING, READ THE SNIPPETS FIRST:
⛔ WHEN RESULTS LOOK WRONG, DO NOT GIVE UP — ITERATE IMMEDIATELY: If search results are all irrelevant (wrong topic, wrong domain, generic encyclopedia entries, piracy sites, brand pages, file format tools, or dictionary entries), DO NOT conclude the information is unavailable. Try a more specific query or a different source. One possible cause is Bing's tokenizer splitting your query words into fragments that collide with unrelated content. Replace fragile/generic terms with INSEPARABLE identifiers — proper nouns, compound terms, subdomain names, or acronyms that the tokenizer CANNOT split. Then immediately re-search. Do not narrate the failure — just try a different formulation. The PRINCIPLE (not the specific domain) matters:
SEARCH STRATEGY (patterns drawn from real-world use):
⚡ NUMERIC DATA CROSS-VERIFICATION:
⛔ DO NOT STOP EARLY — PERSISTENCE IS REQUIRED:
CONDUCT ALL ITERATIONS SILENTLY: When you need multiple rounds of searching and fetching to gather information, run all iterations as tool calls without narrating each step in your reply. Present only the final synthesized answer to the user. Do NOT say things like 'let me search again' or 'I tried searching for X but got Y, let me try Z instead' — just do it and deliver the result. |
| web_fetchA | Fetch a URL and return clean, extracted text content (boilerplate, ads, and nav removed). Use to read articles, documentation pages, or API responses in full. PDF text layers are extracted locally with page labels; unreadable PDFs return an explicit error. OCR is not included. For broad queries, use web_search first, then fetch specific URLs from its results. After fetching, look for technical terms, names, or references you can use as keywords for a better follow-up search. ⚠️ FAILURE IS NORMAL — DO NOT GIVE UP AFTER 1-2 FAILED FETCHES:
RETRY SILENTLY: When a fetch fails, retry with the next URL immediately as another tool call. Do NOT narrate each failure to the user ('this one failed, trying another…'). Only mention failures in your final reply if ALL attempts were exhausted. |
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 occupy clearly separate stages of the retrieval loop: web_search returns ranked titles/URLs/snippets, web_fetch returns full page text for a specific URL. Descriptions explicitly link them (search results tell you which URLs to fetch), so an agent cannot mistake one for the other.
Both names are lowercase snake_case with the same verb_noun shape (web_search, web_fetch) and share a 'web_' prefix, forming a tight, predictable pair. The naming directly mirrors the read/fetch distinction.
Only two tools, but they are exactly the minimal complete pair for a web research server — search without fetch or fetch without search would be useless. It is thin enough that it sits just above the borderline band, and nothing superfluous is included.
Search + fetch covers the full discover-then-read lifecycle, and the descriptions handle recency, multi-engine fallback, and snippet-first triage. Minor gaps remain: no parameter surface documented for site/domain restriction, news/date-scoped variants, or a batch-multi-URL fetch, so some workflows require extra round trips.