Skip to main content
Glama
deenesjakoruzh
merterbak

Grok MCP

by merterbak
OverviewSchemaRelated ServersScoreDiscussions
Python

web_search

Read-only

Answer queries by searching the web across multiple turns, analyzing images, and providing citations in markdown format.

Instructions

Answer a query using agentic real-time web search.

Grok browses the web across multiple turns, optionally inspecting images on
pages, then synthesizes an answer with citations.

Args:
    prompt: Search query or research question.
    model: Grok model used to drive the agent (default `grok-4-1-fast-reasoning`).
    allowed_domains: Restrict search to these domains (max 5, mutually exclusive with excluded).
    excluded_domains: Exclude these domains from search (max 5).
    enable_image_understanding: Let the agent analyze images it encounters.
    include_inline_citations: Embed `[1]`-style citation markers into the answer text.
    max_turns: Cap the agent's reasoning/tool turns.

Returns:
    Markdown with the answer body followed by a `**Sources:**` list of cited URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYes
modelNogrok-4-1-fast-reasoning
allowed_domainsNo
excluded_domainsNo
enable_image_understandingNo
include_inline_citationsNo
max_turnsNo

Tool Definition Quality

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide readOnlyHint=true, but the description adds significant behavioral context beyond that: it explains the multi-turn agentic process, optional image analysis, citation formatting, and output structure. It doesn't contradict annotations and provides rich details about how the tool behaves operationally, though it could mention rate limits or time constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose statement, detailed parameter explanations, and return format. It's appropriately sized for a complex tool, though the opening sentence could be more front-loaded with key differentiators, and some phrasing is slightly verbose (e.g., 'Grok browses the web across multiple turns').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (agentic web search with 7 parameters), no output schema, and minimal annotations, the description does an excellent job covering purpose, parameters, and output format. It explains the multi-turn process and citation system thoroughly. A slight gap exists in not mentioning error conditions or performance expectations, but overall it's highly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining all 7 parameters in the Args section. Each parameter is clearly described with practical meaning (e.g., 'Restrict search to these domains,' 'Cap the agent's reasoning/tool turns'), adding substantial value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('Answer a query using agentic real-time web search') and distinguishes it from siblings by describing its multi-turn browsing behavior and synthesis with citations. It goes beyond just 'search' to explain the agentic nature of the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through phrases like 'Grok browses the web across multiple turns' and 'synthesizes an answer with citations,' suggesting this is for research questions requiring comprehensive answers. However, it doesn't explicitly state when to use this versus alternatives like 'x_search' or 'grok_agent,' leaving some ambiguity about sibling tool differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/merterbak/Grok-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server