Skip to main content
Glama
lalrow

AI Makerspace MCP Demo Server

by lalrow
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

web_search

Search the web for information to answer queries, providing access to current online data through the Tavily API for educational demonstrations.

Instructions

Search the web for information about the given query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:13-17 (handler)
    The handler function for the 'web_search' tool. It is registered via the @mcp.tool() decorator and implements the web search logic using a TavilyClient instance.
    @mcp.tool()
def web_search(query: str) -> str:
    """Search the web for information about the given query"""
    search_results = client.get_search_context(query=query)
    return search_results

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action (search the web) but lacks details on traits like rate limits, authentication needs, result format, or pagination. This is a significant gap for a tool with potential complexity in web search behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core functionality without waste. It's appropriately sized for a simple tool, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool's moderate complexity (web search can involve varied results) and the presence of an output schema, the description is minimally adequate. It covers the basic action but lacks context on usage, behavioral traits, or parameter details, relying on the output schema for return values.

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

Parameters3/5

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

The description adds minimal meaning beyond the input schema, which has 0% description coverage. It implies the 'query' parameter is for web searches but doesn't elaborate on syntax, best practices, or constraints. With one parameter and low schema coverage, the description provides basic context but doesn't fully compensate for the documentation gap.

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 as 'Search the web for information about the given query,' which specifies the verb (search) and resource (web). It distinguishes from siblings like animal_fact or roll_dice by focusing on general web search rather than specific fact domains, though it doesn't explicitly differentiate from potential similar search tools.

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 science_term for domain-specific queries or general contexts where web search is preferred, leaving usage decisions ambiguous for the agent.

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/lalrow/AIE8-MCP-Session'

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