Skip to main content
Glama

search

Perform web searches to retrieve current information from the internet. Enter a query to find relevant results for any topic.

Instructions

Performs web searches and retrieves up-to-date information from the internet. Args: - prompt: Specific query or topic to search for on the internet - limit: Maximum number of results to return (between 1 and 20)

Returns:
- Search results with relevant information about the requested topic

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • main.py:22-36 (handler)
    MCP tool handler for 'search': decorated with @mcp.tool(), delegates to WebTools.search(query), includes docstring schema.
    @mcp.tool()
    async def search(query: str) -> str:
        """Performs web searches and retrieves up-to-date information from the internet.
        Args:
        - prompt: Specific query or topic to search for on the internet
        - limit: Maximum number of results to return (between 1 and 20)
    
        Returns:
        - Search results with relevant information about the requested topic
        """
        try:
            search = webtools.search(query)
            return search
        except Exception as e:
            return f"Error performing search: {str(e)}"
  • Core search logic in WebTools class using FirecrawlApp.search.
    def search(self, query: str):
        try:
            response = self.firecrawl.search(query)
            return response
        except Exception as e:
            return f"Error performing search: {str(e)}"
  • main.py:22-22 (registration)
    Registration decorator for the 'search' tool via FastMCP.
    @mcp.tool()
  • main.py:24-31 (schema)
    Docstring defining input schema (query/prompt, limit) and output for the 'search' tool.
    """Performs web searches and retrieves up-to-date information from the internet.
    Args:
    - prompt: Specific query or topic to search for on the internet
    - limit: Maximum number of results to return (between 1 and 20)
    
    Returns:
    - Search results with relevant information about the requested topic
    """
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions retrieving 'up-to-date information' and a limit on results, which adds some context. However, it doesn't cover critical aspects like rate limits, authentication needs, error handling, or what 'up-to-date' means (e.g., real-time vs. cached). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 and appropriately sized, with a clear purpose statement followed by parameter and return sections. It uses bullet points for readability, and each sentence adds value without unnecessary fluff. However, the parameter mismatch slightly reduces efficiency, but overall it's concise and front-loaded.

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

Completeness2/5

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

Given no annotations, no output schema, and low schema coverage (0%), the description is incomplete. It provides basic purpose and some behavioral hints but lacks details on parameters (due to mismatch), error cases, or output structure. For a web search tool with potential complexity, this leaves the agent under-informed about how to use it effectively.

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

Parameters1/5

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

The description lists two parameters (prompt and limit), but the input schema only has one parameter (query). This creates a contradiction, as 'prompt' in the description doesn't match 'query' in the schema. With 0% schema description coverage and mismatched parameters, the description fails to add meaningful semantics beyond the schema and actually misleads about the tool's inputs.

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

Purpose4/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: 'Performs web searches and retrieves up-to-date information from the internet.' This specifies the verb ('performs web searches') and resource ('information from the internet'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like crawl, extract, or scrape, which likely have overlapping internet-related functions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like crawl, extract, or scrape, nor does it specify scenarios where search is preferred over them. The usage context is implied (web searches for up-to-date information) but lacks explicit when/when-not instructions or comparisons.

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/josemartinrodriguezmortaloni/webSearch-Tools'

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