Skip to main content
Glama
Sign In
webclaw

webclaw

by 0xMassi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

search

Execute web searches to retrieve structured information for AI agents, delivering LLM-optimized results with reduced token usage.

Instructions

Search the web for a query and return structured results. Requires WEBCLAW_API_KEY.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
num_resultsNoNumber of results to return (default: 10)
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It successfully discloses the WEBCLAW_API_KEY requirement and mentions 'structured results', but lacks safety profile disclosure (read-only vs destructive), rate limits, or specific result format details.

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?

Two efficient sentences with no waste. Front-loaded with action ('Search the web'), followed by output description and auth requirement. Every element earns its place.

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?

Adequate for a simple 2-parameter tool with no output schema, covering purpose, auth, and return type. However, gaps remain in distinguishing from functionally similar siblings and detailing what 'structured results' specifically means.

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?

Schema description coverage is 100% with clear descriptions for both 'query' and 'num_results'. Description adds minimal parameter-specific semantics beyond the schema, but baseline 3 is appropriate given comprehensive schema coverage.

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?

Clear verb ('Search') and resource ('the web') with output format specified ('structured results'). However, given siblings like 'crawl', 'scrape', and 'research', it could better differentiate this web search capability from those related 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?

Provides no guidance on when to use this tool versus siblings like 'research', 'crawl', or 'scrape', nor does it mention prerequisites beyond the API key requirement. No 'when-not-to-use' guidance present.

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

Deploy Server

Other Tools