Skip to main content
Glama
Sign In
superhighway-mcp

superhighway-mcp

by patwalls
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

web_search

Search the web in real time and retrieve ranked organic results as JSON. No signup or API key required; pay per search via USDC.

Instructions

Real-time web search. Returns ranked organic results (title, url, snippet) as JSON from a multi-engine metasearch. Paid per call in USDC via x402 — no signup, no API key. Use for fresh facts, research, fact-checking, and grounding/RAG.

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": "web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-20 (default 5).
queryYesThe search query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations, so description carries full burden. Discloses multi-engine metasearch, paid per call via x402, no signup/key needed. Describes output format.

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 concise sentences. First sentence covers purpose and output. Second sentence adds pricing and use cases. Every sentence earns its place.

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?

No output schema, but description explains return fields (title, url, snippet). Covers purpose, pricing, use cases. Parameters documented. Missing pagination details, but acceptable for a search tool.

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 covers 100% of parameters with descriptions. Description adds default for limit (5) and range (1-20), but schema already specifies these. Minimal extra value beyond 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?

Clearly states 'real-time web search' with specific output format (JSON, ranked, with title/url/snippet). Distinguishes from sibling tools by implying general web results.

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

Usage Guidelines4/5

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

Explicit use cases: fresh facts, research, fact-checking, grounding/RAG. Pricing model noted. No direct alternatives named, but sibling list implies scope.

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