Skip to main content
Glama
Sign In

TrollBridge MCP

by io.github.eric-tijerina
OverviewDiscussionsAdmin

bridge_fresh

Mini's TrollBridge — bounties posted in the last 24 hours. TOLLED: $0.005 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_fresh"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses a paid operation ($0.005 USDC via x402) and the exact failure behavior (returns 402 payment instructions instead of data). It does not describe return shape or whether payment is per-call or per-batch, so not quite 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?

Three short sentences, front-loaded with the scope before the payment caveat. The 'Mini's TrollBridge' branding is slightly throwaway but costs almost nothing.

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 one-parameter read tool with no annotations and no output schema, the definition covers scope, cost, payment-failure path, and limit. The only real gap is what a returned bounty entry contains, which a listing tool's caller might want.

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 optional limit already documents range and default (1-200, default 50), so the baseline is 3. The description's 'Optional limit 1-200' restates the schema rather than adding anything new.

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 the resource (bounties) and a precise scope (posted in the last 24 hours), which differentiates it from the sibling bridge_bounties. It never names that sibling directly, but the temporal qualifier is specific enough that an agent can distinguish the two.

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

Usage Guidelines3/5

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

Usage is implied by 'last 24 hours' but there is no explicit when-to-use versus bridge_bounties, and no statement about when a wider window is preferable. The 402 fallback note does tell the agent what happens on non-payment, which is genuine guidance.

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