Skip to main content
Glama
Sign In

TrollBridge MCP

by io.github.eric-tijerina
OverviewDiscussionsAdmin

bridge_yields

Mini's TrollBridge — best DeFi yields right now. 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_yields"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max yields to return (1-50). Default 20."New value: +"Max items to return (1-200). Default 50."
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +200
    • removedInput schema / properties / stablecoinOnly
      Removed value: -{
-  "description": "Only stablecoin pools. Default false.",
-  "type": "boolean"
-}
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral value: a $0.05 USDC x402 toll and the fact that non-payers receive 402 payment instructions instead of data. However, it omits return format, rate limits, and what 'yields' actually contains, so it is only partially transparent for a tool with zero annotation coverage.

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?

It is short and front-loads the identity and the toll, which are the two things an agent most needs. The 'Mini's TrollBridge' branding is minor noise but costs little.

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?

For a single-optional-parameter tool with no output schema and no annotations, the description covers the payment behavior adequately but leaves the actual yield payload format and any rate/result limits unexplained. It is minimally sufficient rather than complete.

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 limit parameter is fully documented there, so the schema does the heavy lifting. The description merely restates 'Optional limit 1-200' without adding format or behavioral meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('best DeFi yields right now') but supplies no verb and does nothing to distinguish it from close siblings like bridge_markets, bridge_opportunities, or bridge_fresh. An agent cannot tell from this text alone why it should pick bridge_yields over those.

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?

It states the payment precondition and the failure path (returns 402 instructions if you can't pay), which is useful context, but gives no guidance on when to use this tool versus the many other bridge_* siblings, nor any exclusions or prerequisites beyond the toll.

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