trollbridge-mcp

bridge_yields

Fetch current DeFi yields, including stablecoin APYs, for yield-hunting agents; pay $0.05 USDC per call via x402 on Base or Solana, or get payment instructions.

Instructions

Mini's TrollBridge — best DeFi yields right now: stablecoin APYs and more, for yield-hunting agents. 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. Optional limit 1-50, stablecoinOnly.

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

Name	Required	Description	Default
`limit`	No	Max yields to return (1-50). Default 20.
`stablecoinOnly`	No	Only stablecoin pools. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Oct 15, 2026

TDQS

A3.7/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 so well: it discloses the tolled pay-per-call model ($0.05 USDC on Base or Solana via x402) and the failure behavior (returns 402 payment instructions instead of data). It omits rate limits and freshness/latency characteristics, but the payment and failure semantics are exactly the kind of non-obvious behavior an agent needs.

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?

Compact and front-loaded: identity, what it returns, cost, failure mode, then params. The branding ('Mini's TrollBridge') is mildly expendable but the rest earns its place with no redundancy.

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 two-parameter, no-output-schema tool, the description covers the essentials: what it returns, the payment gate, and the no-payment fallback. The missing piece is sibling differentiation within a large bridge_* family, which matters here given 17 related tools.

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%, so both parameters (limit and stablecoinOnly, including ranges and defaults) are already fully documented in the schema. The description merely restates 'Optional limit 1-50, stablecoinOnly' and adds no syntax or semantic nuance beyond it, which is the baseline 3 case.

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 specific resource (DeFi yields: stablecoin APYs and more) with a clear scope and identifies the audience (yield-hunting agents). It does not, however, differentiate itself from plausible siblings like bridge_markets or bridge_opportunities, leaving the agent to infer which yield-adjacent endpoint to pick.

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 'for yield-hunting agents' and by the payment note ('If you cannot pay, this tool returns the 402 payment instructions instead of data'), which is genuinely useful when-planning. There is no explicit when-not guidance and no named alternative among the many bridge_* siblings.

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

Deploy Server