Skip to main content
Glama
Sign In

TrollBridge MCP

by io.github.eric-tijerina
OverviewDiscussionsAdmin

bridge_search

Mini's TrollBridge — web search returning agent-ready JSON. TOLLED: $0.05 USDC per call via x402. If you cannot pay, this tool returns the 402 payment instructions instead of data. Optional limit 1-200.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bridge_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (1-200). Default 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max items to return (1-200). Default 50.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / q
      Removed value: -{
-  "description": "Search query.",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "q"
-]
  2. First observed

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 well: it discloses the metered cost ($0.05 USDC via x402) and the concrete failure mode (returns 402 payment instructions instead of data). It does not mention rate limits, result freshness, or whether it is a safe read-only call, leaving minor gaps.

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?

Three short sentences, front-loaded with the function and cost, with no wasted clauses. The 'Mini's TrollBridge' branding is mildly decorative but not harmful.

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?

For a no-annotation, no-output-schema search tool the description covers purpose, cost, payment protocol, failure behavior, and the sole parameter. It omits what corpus is searched and pagination/return-shape detail, but is largely sufficient to invoke correctly.

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% and the single 'limit' parameter is fully documented in the schema. The description only restates 'Optional limit 1-200' without adding format or behavior beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ('web search returning agent-ready JSON') and brands the service, so the core function is unambiguous. It does not explicitly distinguish itself from sibling tools like bridge_fresh or bridge_enrich, which may also surface web content, 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?

There is no guidance on when to pick this over the other 17 bridge_* tools, nor any prerequisites or exclusions. The only conditional statement concerns payment failure, which is a behavioral trait rather than usage direction.

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

All TrollBridge MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources