grok-search
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | |
| get_sourcesB | |
| web_fetchA | |
| web_mapA | |
| get_config_infoA | |
| switch_modelA | |
| toggle_builtin_toolsA | |
| plan_intentA | |
| plan_complexityA | Phase 2: Assess search complexity (1-3). Controls required phases: Level 1 = phases 1-3; Level 2 = phases 1-5; Level 3 = all 6. |
| plan_sub_queryA | Phase 3: Add one sub-query. Call once per sub-query; data accumulates across calls. Set is_revision=true to replace all. |
| plan_search_termB | Phase 4: Add one search term. Call once per term; data accumulates. First call must set approach. |
| plan_tool_mappingC | Phase 5: Map a sub-query to a tool. Call once per mapping; data accumulates. |
| plan_executionC | Phase 6: Define execution order. parallel_groups: semicolon-separated groups of comma-separated IDs (e.g., 'sq1,sq2;sq3'). |
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 13 tools
The core search/fetch tools (web_search, get_sources, web_fetch, web_map) are clearly distinct. The six planning tools (plan_*) are sequential phases with explicit ordering, so though they share a prefix, each has a unique purpose. Minor risk of confusion between plan_sub_query and plan_search_term, but descriptions clarify the difference.
All tools use snake_case and follow a clear verb_noun pattern (e.g., web_search, get_sources, switch_model, plan_intent). The planning tools uniformly start with 'plan_' and the rest use action verbs. Consistent naming across the entire set.
13 tools is a moderate count. The core search operations (search, fetch, map, sources) justify their presence, and the 6 planning tools form a structured workflow. While it feels slightly heavy for a search server, every tool has a defined role and the count is not excessive.
The tool set covers the search lifecycle: planning (plan_*), executing search (web_search), retrieving sources (get_sources), fetching content (web_fetch), and site exploration (web_map). Configuration and integration tools (get_config_info, switch_model, toggle_builtin_tools) round out the surface. Minor gap: no explicit tool to clear or manage cached sessions, but that is not a core search operation.