agy-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_BIN | No | agy 可执行文件路径 | agy |
| AGY_SEARCH_MODEL | No | 默认模型 id（`agy models` 第一列） | gemini-3.8-flash-high |
| AGY_SEARCH_EFFORT | No | 可选的 `--effort`（low/medium/high/xhigh/max） | |
| AGY_SEARCH_RETRIES | No | 硬超时后的重试次数 | 1 |
| AGY_SEARCH_TIMEOUT | No | 单次调用硬超时（秒） | 120 |
| AGY_SEARCH_MAX_CHARS | No | 返回文本上限，超出截断 | 8000 |
| AGY_SEARCH_RESOLVE_SOURCES | No | 是否把 grounding 跳转链接解析成真实 URL | 1 |
| AGY_SEARCH_RESOLVE_TIMEOUT | No | 单条链接解析超时（秒） | 4 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the web and return a concise answer with source URLs. Args: query: Natural-language search query. |
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
There is only one tool, so there is no possibility of misselection between tools. Its purpose (web search with a natural-language query) is unambiguous.
The single name 'search' is clear and lowercase, but it lacks the verb_noun form used in the calibration examples and is generic enough to be ambiguous outside the server's context.
One tool is thin even for a narrowly scoped search server; there is no companion operation such as fetching or opening a specific source URL. The surface is minimal but not mismatched to a single-purpose server.
Search with source URLs covers the core lookup need, but agents cannot retrieve or expand a specific source page, leaving a notable gap in the research workflow. Minor workarounds exist by re-querying.