trollbridge-mcp

bridge_search

Searches the web for AI agents and returns title, URL, and snippet as JSON. Requires a query and $0.05 USDC per call via x402 on Base or Solana; unpaid calls return 402 payment instructions.

Instructions

Mini's TrollBridge — web search for agents: title, url, snippet per result, agent-ready JSON. TOLLED: $0.05 USDC per call on Base or Solana via x402. If you cannot pay, this tool returns the 402 payment instructions instead of data. Requires q.

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": {
      "q": "<q>"
    },
    "name": "bridge_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Oct 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the tool is tolled at $0.05 USDC per call, names the payment rails (Base/Solana via x402), and — critically — states that an unpaid call returns 402 payment instructions instead of data. It omits rate limits, result counts, and pagination, so not a 5.

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?

Front-loaded with the core purpose, then the payment constraint and requirement. Almost every clause earns its place, though the branding descriptor 'Mini's TrollBridge' adds little for an agent.

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?

There is no output schema, but the description compensates by describing the return fields and, importantly, the 402 alternative response. For a one-parameter tool this is nearly complete; only pagination/result-limit behavior is missing.

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 coverage is 100% and the single parameter 'q' is fully documented in the schema as 'Search query.' The description only adds 'Requires q', which restates the required flag rather than adding syntax or semantics. Baseline 3 is appropriate.

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?

States a clear verb+resource ('web search for agents') and even lists the return shape (title, url, snippet, JSON). This cleanly separates it from the data-feed siblings (bridge_prices, bridge_gas, bridge_markets), but it never explicitly names or contrasts an alternative, so it stops short of a 5.

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 explains payment terms and that 'q' is required, but gives no when-to-use guidance or when-not-to-use exclusions relative to the many bridge_* siblings. An agent gets no routing help beyond inferring that 'search' means web search.

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

Deploy Server