Web Search Neo
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 |
|---|---|
| web_infoB | Read the contract, the page, the console, the network, or search/browser state. Called with no arguments it returns the whole contract, including recipes and
common mistakes, so no external skill file is needed. Every result (dict
payloads) also carries the current local date/time and UTC-offset region
under the top-level |
| web_actionA | Execute 1-32 ordered actions. Read web_info action_schema before unfamiliar actions or after validation errors. fill uses fields={CSS_selector: value}. Use a unique session_id per task/agent; never close another agent's tabs. |
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 completely distinct roles: web_action executes operations, while web_info retrieves state and context. There is no functional overlap, so an agent should never confuse them.
Both tools follow the same 'web_' prefix with a clear noun suffix ('action' vs 'info'). The naming is consistent, short, and predictable, even though it uses nouns rather than verb_noun.
Two tools is on the low end and feels thin for a web automation domain. While every tool is broad and earns its place, the server likely relies on complex schemas to compensate for the minimal count.
The action/info split covers the fundamental read-operate cycle of browser automation, and web_action's ordered actions suggest broad capability. Minor gaps may exist (e.g., no obvious dedicated session-management tool), but the design appears to cover core needs.