Skip to main content
Glama
Sign In

TrollBridge MCP

by io.github.eric-tijerina
OverviewDiscussionsAdmin

bridge_models

Mini's TrollBridge — AI model catalog: 100+ models with per-token pricing. TOLLED: $0.02 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_models"
  }
}

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, the description carries the full behavioral burden and does well: it discloses a mandatory $0.02 USDC cost via x402 and, crucially, the failure mode (returns 402 payment instructions instead of data). It omits return shape, pagination behavior, and any rate limits beyond per-call payment.

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 catalog purpose, then the toll and failure mode — the information an agent most needs to decide. Dense but every clause carries signal; no filler.

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 catalog tool, the description covers identity, scope, cost, and the payment-failure path. The main residual gap is return format, but a model catalog returning a model list is a reasonable expectation.

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, so the baseline is 3. The description merely restates 'Optional limit 1-200,' adding nothing beyond the schema's own bounds and default.

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?

Names a concrete resource (AI model catalog) with useful scope detail: 100+ models and per-token pricing. It is distinguishable from siblings like bridge_prices or bridge_tools by resource, though it never explicitly contrasts itself with any of them.

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 the catalog framing and the payment note, but there is no explicit when-to-use, when-not-to-use, or named alternative among the 17 sibling tools. An agent must infer that this is the tool for browsing models rather than pricing or markets.

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